[Remove Vuetify from Studio] Saved searches dialogs

[MisRob]

🙂 Looking for an issue? Welcome! This issue is open for contribution. If this is the first time you’re requesting an issue, please:

• Read Contributing guidelines carefully. Pay extra attention to Using generative AI. Pull requests and comments that don’t follow the guidelines won’t be answered.
• Confirm that you’ve read the guidelines in your comment.

Sub-issue of #5060.

Complexity: Low

Summary

Migrate the following two dialogs in Edit channel > Import from other channels from Vuetify to Kolibri Design System.

Several VList... components, VDivider, and MessageDialog and ActionLink built with several Vuetify components, are currently used.

Remove these dependencies on Vuetify in this specific location by:

• Replace MessageDialog by KModal
• Replace ActionLink with the most suitable KDS button or link components
• Replace VList... and VDivider by custom styles and semantic markup

Ensure that the dialog work exactly as before. Do not modify ActionLink or MessageDialog. Do not refactor any other areas.

How to get there

• Login as a@a.com with password a
• Go to Channels > Imported channel
• Click Add > Import from channels
• Search for "video"
• Click Save search
• Click Saved searches
• Click Delete search icon

Guidance

• Find detailed guidance with many code examples in KDS documentation
• Read the project for more useful references

Out of Scope

• Do not refactor any other areas of the codebase
• Do not modify ActionLink or MessageDialog

Expected UI/UX changes

• Minor visual differences naturally stemming from the use of KDS

Acceptance criteria

These are general acceptance criteria for the project. For each sub-issue, consider which are relevant.

General

• The specification above is followed.
• Except for "Expected UI/UX changes," there are no functional or visual differences in user experience.
• There are no ::v-deep or /deep/ selectors.
• All user interactions are manually tested with no regressions.
• Pull request includes screenshots.

a11y and i18n

See the project's "Guidance" for useful references.

• Implementation meets a11y standards
• All components are LTR and RTL compliant (preview with pnpm run devserver since :hot doesn't render RTL properly)
• All user-facing strings are translated properly
• The notranslate class been added to elements that shouldn't be translated by Google Chrome's automatic translation feature (e.g. user-generated text)
• Mobile experience is reasonable

Unit tests

• If there is a unit test suite already, it is meaningfully updated (even if tests don't fail)
• If there is no unit test suite, a new one is created. Do not use obsolete @vue/test-utils approach. Instead, use @testing-library/vue (Vue Testing Library).

[vtushar06]

Hii @MisRob, can I work on this issue as well, as of now I am not assigned to any issue, would love to resolve this, Thanks

[MisRob]

Hi @vtushar06 - I've just assigned you another issue. Also, I'm just preparing a medium complexity issue for you that you asked for and will share soon. If you're still interested in it, perhaps we can leave smaller issues for new contributors?

[vtushar06]

Sure thing @MisRob! No problem at all — I completely understand. I’m glad you’re preparing a medium complexity issue.

[JanaKocakova]

Hello!
I’d like to contribute to this issue. It looks like a good learning opportunity. Could you please assign me so I can start working on it? Thank you in advance.

[MisRob]

@JanaKocakova Ahoj Jani, zdravím do sousedního Slovenska :)

Happy to assign you. There's plenty of links and guidance in the parent project that will be helpful.

Out of curiosity - have you found us via Hacktoberfest or somehow else?

[JanaKocakova]

Zdravím :).

Thanks I will check parent project / issue for more info.

I just randomly stumbled upon this project via GitHub search when I was looking for some beginner friendly issue.

[MisRob]

Good then, thanks for sharing.