Update workflow to new version #517
-
|
Hi,
Sorry if this is already explained in the documentation and I missed it! (Thank you for the fantastic work!) |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
I think the best way if you haven't made too many changes is to delete the spartan directory and remove the paths from the tsconfig and rerun the cli. but this is a main reason we are still in alpha because this process is very rough still |
Beta Was this translation helpful? Give feedback.
-
|
Okay, that worked better than expected - thx! I was a little bit confused by the brain imports. Is the intended way using |
Beta Was this translation helpful? Give feedback.
-
|
Ended up with the same flow. We have adapted the project in production (yes this is an alpha and we love to live on the edge) and migrating to latest versions basically weekly (toughest was when all imports were changed). My flow so far that worked is the delete flow. But perhaps we can add a migrator to the cli to make this simpler? |
Beta Was this translation helpful? Give feedback.
-
|
Do you use the default spartan styling for your project? We are too using it in a production application but with an external designer, so we have to modify every hlm cva section to style it properly and add custom properties. Maybe it would be easier to apply the changes with a version comparison page, where you input your current spartan vesion and the version you want to update to. |
Beta Was this translation helpful? Give feedback.
I think the best way if you haven't made too many changes is to delete the spartan directory and remove the paths from the tsconfig and rerun the cli. but this is a main reason we are still in alpha because this process is very rough still