Create a new branch dev for the script setup migration

Hello,

@VividLemon, @mariusa , @aceofwings,

Currently, there are many changes to transform all the components to script setup. I think it’s a very good thing to switch to script setup, and it’s also the way I work on all my projects in vue+typescript

But if you run the dev app npm run dev, there are certain things that don’t work anymore and it’s not easy to know if it was the case before … and if it’s linked to the migration

Could we create a dev branch for this migration and merge the pull-requests related to the migration on it?

We could also remove all commits related to this migration from main. To be able to do a better review of the migration and to be able to compare with the pre-migration version (using a Pull Request).

You can do this by creating the dev branch from main

git checkout -b dev
git push --set-upstream origin dev

Remove main

git branch -D main

Return to this commit a9f8b95f6636631a8de0 (just before the migration)

git checkout a9f8b95f6636631a8de0

Recreate the main branch from this commit

git switch -c main

Force-push it

git push -f --set-upstream origin main

That would allow us to do a better review of the migration to script setup and compare

I did the test here on my repo fork, then here is the PR of the new dev branch on the main https://github.com/messenjer/bootstrap-vue-3/pull/1/files

What do you think?

Mathieu

[mariusa]

Turning all props to not be required, causes no errors (besides like two, fixable issues). Should I pr to have all props not be required?

Great, let’s do this!

[aceofwings]

Ill take a stab. Lets merge in the current fixes and go from there