🤖 dprint
#45
Merged
🤖 dprint
#45
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
jorenham
added
💄 UI
nstarman
approved these changes
Jul 17, 2025
|
The style is alright. The consistency is 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.
I configured it for markdown, toml yaml, and json[c].
There aren't many config options, especially for toml. Personally, I'm not very enthusiastic about the style, but I can live with it. And I suppose that those who like
blackmight consider the lack of configurability a feature.I've been using
dprintforscipy-stubsfor a while now, and I've gotten used to the style. But style aside,dprinthas been smooth sailing so far, so I'd certainly recommend it (but you could probably already tell by the existence of PR :p).Oh and it's written in rust, BTW.
https://dprint.dev/