Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate Elemental to be Vue3 compliant #12182

Closed
aalves08 opened this issue Oct 9, 2024 · 2 comments · Fixed by rancher/elemental-ui#223
Closed

Migrate Elemental to be Vue3 compliant #12182

aalves08 opened this issue Oct 9, 2024 · 2 comments · Fixed by rancher/elemental-ui#223
Assignees
Labels
area/extensions area/vue3 Bugs and technical debts as outcome to the Vue3 migration QA/None
Milestone

Comments

@aalves08
Copy link
Collaborator

aalves08 commented Oct 9, 2024

Migrate Elemental to be Vue3 compliant

@aalves08 aalves08 self-assigned this Oct 9, 2024
@aalves08 aalves08 added area/extensions area/vue3 Bugs and technical debts as outcome to the Vue3 migration labels Oct 9, 2024
@aalves08 aalves08 added this to the v2.11.0 milestone Oct 9, 2024
@github-actions github-actions bot added QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this and removed area/extensions area/vue3 Bugs and technical debts as outcome to the Vue3 migration labels Oct 9, 2024
@aalves08 aalves08 added area/extensions area/vue3 Bugs and technical debts as outcome to the Vue3 migration QA/None and removed QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this labels Oct 9, 2024
@richard-cox
Copy link
Member

@aalves08 should this be 2.10.0?

@aalves08
Copy link
Collaborator Author

aalves08 commented Oct 25, 2024

Yes. 👍 fixed. Thanks

@aalves08 aalves08 modified the milestones: v2.11.0, v2.10.0 Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/extensions area/vue3 Bugs and technical debts as outcome to the Vue3 migration QA/None
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants