I've been thinking about designing a solution to automate the process of updating an old local version of shadcn-vue with the latest remote version. There are some things we should consider (in no particular order):
Updating Strategy: Since the code is subject to change, we should consider a conflict resolving strategy per file (similar to how GIT handles conflicts).
We should provide a developer-friendly way to resolve conflicts.
I'm thinking of leveraging GIT itself to do the heavy lifting
Breaking Changes: Some of the changes in the remote version might be breaking changes, so this list should be reported to the user or potentially abort the updating process
Update Checking: The CLI should be able to check for updates and inform the user of any new updates.
Useful Information: We could also provide some additional information including:
generating changelog that user should expect (could be done with #437)
amount of commits behind remote registry
Please provide any feedback or suggestions. It would be greatly appreciated. Thank you!
Additional information
[x] I intend to submit a PR for this feature.
[ ] I have already implemented and/or tested this feature.
Describe the feature
I've been thinking about designing a solution to automate the process of updating an old local version of
shadcn-vuewith the latest remote version. There are some things we should consider (in no particular order):Please provide any feedback or suggestions. It would be greatly appreciated. Thank you!
Additional information