[Remove Vuetify from Studio] 'Unsaved changes' modal in Channels - New collection

[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

Remove Vuetify from Unsaved changes modal in Channels > Collections > New collection:

MessageDialog.vue built with several Vuetify components is currently used for this modal:

studio/contentcuration/contentcuration/frontend/channelList/views/ChannelSet/ChannelSetModal.vue

Lines 158 to 180 in a8476ad

	<MessageDialog
	v-model="showUnsavedDialog"
	:header="$tr('unsavedChangesHeader')"
	:text="$tr('unsavedChangesText')"
	data-test="dialog-unsaved"
	:data-test-visible="showUnsavedDialog"
	>
	<template #buttons>
	<VSpacer />
	<VBtn
	flat
	@click="confirmCancel"
	>
	{{ $tr('closeButton') }}
	</VBtn>
	<VBtn
	color="primary"
	@click="save"
	>
	{{ $tr('saveButton') }}
	</VBtn>
	</template>
	</MessageDialog>

Remove dependencies on Vuetify by using KModal instead of MessageDialog.

Do not modify MessageDialog.vue or how it's used at another places.

How to get there

• Login as user@a.com with password a
• Go to Channels > Collections
• Click New collection button
• Add some text to Collection name input
• Click the close button in the top bar

Guidance

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

Out of Scope

• Do not modify MessageDialog.vue
• Do not refactor any other areas of the codebase

Expected UI/UX changes

• Minor visual differences naturally stemming from the use of KDS

Acceptance criteria

General

• The specification above is followed.
• Except for "Expected UI/UX changes," there are no functional or visual differences in user experience.
• 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).

[Kartikayy007]

hi @MisRob, can you assign me this issue?

[Kartikayy007]

@MisRob please take look

[akolson]

HI @Kartikayy007! Yes--sure. Please feel free to let us know incase you have any questions or comments regarding the issue. Thanks you so much.

[AvaniNGoswami]

Hi! I’ve read the contributing guidelines and would like to work on this issue. I’ll replace MessageDialog with KModal in ChannelSetModal.vue and will follow the acceptance criteria. Could you please assign this to me?

[MisRob]

Hi @AvaniNGoswami, thanks! We have already received a pull request for this issue, even though it's unclear whether @Kartikayy007 plans to come back to resolve feedback. Let's wait for some time if we hear back.

You're welcome to keep an eye on the list of unassigned help wanted issues. There are none currently, but we add new ones regularly, usually at least once per week.

[vtushar06]

Hii @MisRob, Can you assign this issue to me if current contributor is not active on this.thanks

[MisRob]

Hi @vtushar06, since @Kartikayy007 didn't respond here, we'd be happy to let you finish that work. Do you think you could push right to #5306 based on review feedback so that the review is not lost?

[vtushar06]

Yes, sure @MisRob! I’ll continue the work on PR #5306 and push the changes based on the existing review feedback.

[MisRob]

Thank you @vtushar06, that's helpful