Repository navigation
Fix line-length path in --config example - #28392
Merged
Merged
Conversation
line-length is a global option, not under `lint.` This was introduced in astral-sh#25013, after which astral-sh#25389 attempted to fix it. However, that change was made in autogenerated docs only (instead of fixing it at the source), and thus the fix was undone again in astral-sh#25396. This instead fixes the issue in the source code, followed by a `cargo dev generate-all`.
ntBre
added
the
documentation
ntBre
changed the title
line-length path in --config example
|
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
line-length is a global option, not under
lint.This was introduced in #25013, after which #25389 attempted to fix it. However, that change was made in autogenerated docs only (instead of fixing it at the source), and thus the fix was undone again in #25396.
This instead fixes the issue in the source code, followed by a
cargo dev generate-all.