Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Create a new branch dev for the script setup migration

See original GitHub issue


@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

What do you think?


Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:10 (1 by maintainers)

github_iconTop GitHub Comments

mariusacommented, Jun 29, 2022

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!

aceofwingscommented, Jun 29, 2022

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

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to manage Migrations in a project with multiple branches?
One way would be to merge, then delete all migration-files created while the branches were separate, and then create one new migration file...
Read more >
Basic Branching and Merging - Git SCM
Create a branch for a new user story you're working on. Do some work in that branch. At this stage, you'll receive a...
Read more >
Migrating to a new Git repository | Looker - Google Cloud
At first, your Git provider's UI will only show the master branch and its history. Other branches and their history will appear the...
Read more >
Migration Script is not working in Branches — Redgate forums
Hi Team, I have Dev,Test and Stage branches created in TFS. Dev I have linked 'Dev Branch' to the Red gate Source control...
Read more >
Git Feature Branch Workflow | Atlassian Git Tutorial
Create a new-branch ... Use a separate branch for each feature or issue you work on. After creating a branch, check it out...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found