Merged
Conversation
Collaborator
|
LGTM. |
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
2 participants
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.
Now that we have a proper python structure, I wanted to bring a little more consistency to the code. This PR has 3 commits: first I added ruff and ty config options to pyproject.toml, then I ran ruff format to adjust non-logical code structure, and then I ran ruff check --fix to adjust (probably) non-functional fixes to things like fstrings and import order.
This will make it easier to diff the code later if we normalize linting rules. It's possible to add a CI check / or git hook to automatically do it, but I find its easier to just rerun it every so often.