Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
fix(toml): Error on
[project]
in Edition 2024 #13747fix(toml): Error on
[project]
in Edition 2024 #13747Changes from all commits
8181bc8
77f96f5
c9325c9
2f4d3df
9fb428b
ca699d2
1ec1455
d5606b2
98298d4
cbd9def
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Sorry, there seems to be some problem here, it doesn't fetch all members of the workspace. If the members contain
[project]
, thencargo fix --edition
won't complete the migration either.Is this intentional, or am I misinterpreting?
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.
We do filter by the
--package
flag which is us just doing what the user told us. I'm not seeing how presence of[proiject]
causes a problem. We also have a test showing that it works.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.
Sorry, I don't seem to have been clear.
What I meant was that if the members in the workspace use
[project]
instead of[package]
, then executing the commandcargo fix --edition
in the workspace does not modify the members.I'm wondering if the changes should be done on all members at once.
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 think I'm still missing the problem case.
Could you create a test case to demonstrate it?
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 there is a workspace
ws
containing the memberhello
.which:
After running
cargo fix --edition --allow-no-vcs
in the workspace. Thecargo.toml
ofws
completes the modification, but thecargo.toml
of memberhello
does not.I think both should be modified to
[package]
here.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've written that up as a test case which is passing.
Yes, we aren't migrating
hello
'sCargo.toml
but we also aren't migratinghello
ssrc/lib.rs
. Manifest and rust migration should be done hand-in-hand. The user has to opt-in to migratinghello
with the--workspace
flag.cargo fix --edition --workspace
will migrate both packages, manifest and rust.