Integrate ruff for formatting - #3
Merged
Merged
Conversation
* Refactor all public class, function, and module docstrings to follow Google style and ruff with ≤80 character lines. * Add missing docstrings and expand existing ones for clarity, including `Args`, `Returns`, and `Notes` sections. * Document exception cases and special behaviors in relevant docstrings. * No functional code changes; documentation only.
saudzahirr
approved these changes
Jul 26, 2025
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.
This pull request applies Ruff's automatic code formatting and linting to the entire codebase. By standardizing code style, it improves readability, maintains consistency, and helps ensure adherence to best practices. No functional changes have been made—this PR is focused solely on style updates.