Add ruff configuration to offer standardized way for formatting #137
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
Added a basic configuration of ruff in order to try to standardize formatting in the future using @prithviulm first suggestion and optimizing it for current code style.
"
or'
.,
will remain in one line, up until they reach the max 120 chars, before being broken into multiline parameter declarationsAlso some linting configs are done to prevent ruff, when being used in an IDE, displaying too many warnings and errors.
In #155 this formatting was already used in commits fdef371, 35000a4, 60943c2 and 60943c2.
Motivation and Context
In the recent PR's we often had the question, how new code should be formatted. This configuration is a first attempt at somewhat standardizing and offering a tool to automatically format newly contributed code.
How Has This Been Tested?
Using the configuration to make the changes in fdef371, 35000a4, 60943c2 and 60943c2.
Types of changes
Checklist:
/docs/changelog.md
.(syntax, indentation, mutable default values, etc.).