Skip to content

[Remove Vuetify from Studio] Send e-mail dialog #5425

@MisRob

Description

@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: Medium

Summary

Remove Vuetify from the Send e-mail dialog in Administration > Users (including Draft in progress alert)

The dialog is currently built with several Vuetify components, such as VDialog, VChip, VTextField, and others.

Remove dependencies on Vuetify in this specific location by:

  • Replace VDialog and ConfirmationDialog by KModal
  • Replace VFlex and VLayout by custom styles
  • Replace VForm by <form>
  • Replace VTextField and VTextarea by KTextbox
  • Replace VTooltip by KTooltip
  • Use generateFormMixin for validation
  • Create a new custom StudioChip component to replace VChip

Ensure that the dialog work exactly as before. Do not refactor any other areas.

How to get there

  • Login as [email protected] with password a
  • Go to Administration > Users
  • Select few users in the table
  • Click Email

Guidance

Out of Scope

  • 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).

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions