-
Notifications
You must be signed in to change notification settings - Fork 11.7k
[package-alt] rename-from improvements #24112
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
| root::a::b::d1 refers to { local = "../d1", ... } | ||
| root::a::c::d2 refers to { local = "../d2", ... } |
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.
I don't understand the meaning of the ...
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.
Is it supposed to be any other data given in the toml?
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.
yes. should I leave it out?
eef300f to
ac57960
Compare
Changed a few things about rename-from checks: - we only check the root package - we produce much better error messages - the legacy code paths are clearer - most of the large legacy tests have been split up and the error messages snapshotted
Description
This PR changes a few things about rename-from checks:
Test plan
Updated unit tests
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.