infra: introduce dprint for easier formatting #4125
Merged
Conversation
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
This appears to still work with pulldown-cmark, but not necessarily in all renderers, and (more to the point at present) is not compatible with dprint, which does not like the line wrapping that way!
No more need to manually wrap lines? GREAT.
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.
No more need to manually wrap lines? SOUNDS GREAT.
This PR:
.git-blame-ignore-revsfile to make it sogit blamewill skip the formatting commit on GitHub (you may want to wire this up locally!).Future PRs will likely configure a GitHub Action to automatically run
dprint fmtafter commit, inspired by how the DefinitelyTyped project does it, and may apply this same change to the nostarch output (though likely as part of the nostarch script).Fixes #3922