chore: add ruff linter and code formatter
#166
Merged
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
This pull request does not include any functionality changes. It introduces a faster and more streamlined linter and code formatted tool and applies some suggested code formatting rules.
Changes include:
Updates the linter and code formatting tools used.
rufflinter and code formatted tool.pyupgrade,isort,autoflakeandblacktools.setup.cfgfile with a modernpyproject.tomlequivalent.Applies improvements suggested by the tool:
__all__definitions to the__init__.pyfiles as a best practice for exposing the SDK's public API to developer IDEs.Fixes a few minor issues in the examples and unit tests I identified while working on updating things:
setup.pyfiles using incorrect header comment blocks.api_test, which may have causedtest_500_error_retrynot to be run as intended.Ensures the
partial_headerblock is imported in all Python source files.References
Please review
DXAZT-368for additional context.Generated from: openfga/sdk-generator#478
Review Checklist
main