chore: point ty at the api venv #11
No reviewers
Labels
No labels
bug
chore
data
feature
frontend
good first issue
intermediate
needs/docs
needs/research
needs/upstream
type/bug
type/external
type/feature
type/refactor
urgency
high
urgency
immediate
urgency
low
urgency
medium
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
ScottyLabs/cal!11
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/ty-api-venv"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
ty runs from the repository root, where there is no pyproject.toml or
venv, so every third-party import in api/ was unresolved. This adds a
root ty.toml with
environment.python = "api/.venv"andenvironment.root = ["api"]. The explicit setting also wins over thedevenv shell's VIRTUAL_ENV.
With ty 0.0.73 (the nixpkgs pin) after
cd api && uv sync --extra dev:210 diagnostics before, 108 after. What is left is genuine:
x: T = None, same as RUF013)missing SIScraper export)
That is too many to fix here, so the hook stays disabled and its comment
in devenv.nix now describes what is left. Turning it on also needs
api/.venv in the devenv shell, since the shared module only runs uv sync
for a root pyproject.toml.
Deferred ruff groups, counts only (ruff 0.16.3): UP 214, BLE001 68,
DTZ 48, RUF013 21. The configured rule set is clean.
Generated with Claude Code
358b72e64d7b933b54f4