-
-
Notifications
You must be signed in to change notification settings - Fork 251
WIP: V12 migration guide #1048
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
base: master
Are you sure you want to change the base?
WIP: V12 migration guide #1048
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Deploying rescript-lang-org with
|
Latest commit: |
221ebb3
|
Status: | ✅ Deploy successful! |
Preview URL: | https://0b98efeb.rescript-lang.pages.dev |
Branch Preview URL: | https://v12-migration-guide.rescript-lang.pages.dev |
|
|
||
## Replacements | ||
|
||
Some typical name changes include: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we create migrations for each of these, this section can be replaced with an explanation of how to use the migration tool
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The migration guide will also mention changes in rescript.json and stuff.
Except we will somehow auto-migrate those changes as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also at the very least there are some prerequisites to migration, like v11 in uncurried mode. So the migration guide will be required still, albeit a lot smaller than before the migrations were a thing.
No description provided.