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

Move to Vue 3 composition (instead of options) #1148

Open
raphodn opened this issue Dec 19, 2024 · 1 comment
Open

Move to Vue 3 composition (instead of options) #1148

raphodn opened this issue Dec 19, 2024 · 1 comment
Labels

Comments

@raphodn
Copy link
Member

raphodn commented Dec 19, 2024

Story

In Vue 3 there is two different ways to write code:

  • the "old" options API
  • the "new" composition API

https://vuejs.org/guide/introduction.html#api-styles

Why

Most of the Vue 3 projects out there are written in composition.
To help newcomers, but also our friend Copilot 🤖 , we should start thinking of migrating to composition API.

How

  • personally I've never used composition before. But at work we're doing the switch over the coming months (from Vue 2 options to Vue 3 composition). So a good time to learn and test :)
  • component by component ?
    • and take the time to create new components if some are too complex
@raphodn raphodn added the DevOps label Dec 19, 2024
@raphodn raphodn changed the title Move to Vue 3 composition Move to Vue 3 composition (instead of options) Dec 19, 2024
@TTalex
Copy link
Collaborator

TTalex commented Dec 21, 2024

Makes me think we could have the same arguments for moving to typescript.

It would help reduce some of the head scratching with variable names / content across components. 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Backlog
Development

No branches or pull requests

2 participants