Add a linter and code formatter to enforce code quality

[natekspencer]

To help improve long-term maintainability and consistency, I’d like to propose adding a linter and formatter to the project.

There are a few areas where tooling could help: unused imports, inconsistent spacing, and general style differences across files. These aren’t major issues, but they can add friction when reading code or submitting changes. Introducing a standardized tool would automatically catch and correct most of these, keeping the codebase clean without requiring manual review for style.

Benefits:

• Consistent formatting across the repository
• Automatic detection of unused imports/variables
• Clearer diffs and smoother PR reviews
• Lower barrier to entry for contributors

A single tool that handles both linting and formatting, such as Ruff, could be a good fit, but the specific choice can follow project preference. I’m happy to help set up or configure whatever you decide.

[FeliGoblin]

+1 for this. I'm a fan of Ruff

[jjjonesjr33]

I’ll be honest — I’m not very familiar with Ruff. Someone previously tried integrating flake8 as well (see PR #11), so this isn’t entirely new territory.

That said, I took a crash course on Ruff this morning and have already fixed a ton of issues in my local dev environment. Once everything is cleaned up and running smoothly, I’ll work on getting the changes pushed.

[natekspencer]

I also took a stab at it today: https://github.com/natekspencer/petlibro/tree/ruff

[szymon-romanko]

While at it, maybe its worth adding a tool for static code analysis, like ty (from creators of ruff) or pyright (from microsoft)?

[natekspencer]

Agreed it should also add something like this

[natekspencer]

ty is still alpha, so that probably shouldn't be adopted yet