learningequality / learningequality/studio
[Remove Vuetify from Studio] Replace the remaining VAutocomplete dropdowns with KMultiSelect
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 191
- Forks
- 307
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.
Overview
Studio still uses the Vuetify component VAutocomplete in three shared form components. The Kolibri Design System now has KMultiSelect, which does the same job. Two components already made this change, so the pattern is set.
Scope
Included
contentcuration/contentcuration/frontend/shared/views/LanguageDropdown.vuecontentcuration/contentcuration/frontend/shared/views/contentNodeFields/CompletionOptions/ActivityDuration.vuecontentcuration/contentcuration/frontend/shared/views/form/CountryField.vuecontentcuration/contentcuration/frontend/shared/views/contentNodeFields/CategoryOptions.vue- The files that use these components, where they pass Vuetify props to the dropdown.
- The tests for these components.
Excluded:
- The other Vuetify components in the same files.
DropdownWrapper, because other components still use it.- The removal of
VAutocompletefromshared/app.js. That happens after every use of it is gone.
Guidance
- Set up Studio with the steps in
README.md. - Read the
KMultiSelectdocumentation: https://design-system.learningequality.org/kmultiselect - Follow the two finished examples:
LanguageFilter.vue(#6093) andCategoryOptions.vue(#6092). - Shared accessibility strings live in
shared/strings/commonStrings.js. Add a new string only when no shared string exists. KMultiSelectuses the propsinvalidandinvalidText. It does not use the Vuetifyrulesprop.
Strategy
Testing Requirements
- Write new tests with Vue Testing Library. Do not add tests with
@vue/test-utils. pnpm testandpre-commit run --all-filesmust pass on each task.
AI usage
I used Claude Code to draft this issue. I set the scope, checked the file list, and wrote the guidance.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the four listed Vue components and compare them with the completed LanguageFilter.vue and CategoryOptions.vue examples, then read the KMultiSelect documentation. Update the remaining dropdown usages and their component tests, ensuring the listed test commands pass and no VAutocomplete usage remains in the scoped files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 20/100