Skip to content

Start a refactor #2724

@Syzygy106

Description

@Syzygy106

Describe

When I run tests on main, about 50 are failing. Hard to add new features when I can't tell if I broke something or if it was already broken. So before any other features - we need to stabilize current version. Would it make sense to create a refactor protected branch where we can work on improvements without risking main? Fix tests along the way, then merge back when stable.

Specification

  • Fix tests
  • Run linter
  • Migrate to new syntax (Python 3.10+)
  • SQLAlchemy 2.0
  • UV
  • Delete deprecated code
  • Migrate dependency declarations from setup.py to pyproject.toml
  • Add Alembic for database schema migrations
  • Remove setup.cfg as it's replaced by ruff configuration
  • Enable additional ruff rules for code quality improvements

Dependencies

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions