CAIP-9 extend tooling with ruff formatter #372
Merged
+4,406
−3,248
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
broHeryk
force-pushed
the
CAIP-9-extend-tooling
branch
from
39bc1d2 to
c3577ec
Compare
catalinsymphony
approved these changes
Aug 12, 2025
Collaborator
catalinsymphony
left a comment
catalinsymphony
left a comment
There was a problem hiding this comment.
It looks much better ... I noticed the docstrings do not have the 88 character limit, but looks ok.
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.
Description
Closes CAIP-9
This PR consists of re-formatted files(They create a lot of noise). Files that are important to check:
After setting up per-commit git hooks, the linter/formatter(ruff) will be running automatically as shown on the screenshot below (you might need to re-run the commit command in case of a failed formatter check)
Checklist