Skip to content

Comments

chore(typing): scope ty checks and allow optional import#5

Open
RazorBackRoar wants to merge 21 commits intomainfrom
codex/ty-scope-nexus-20260218
Open

chore(typing): scope ty checks and allow optional import#5
RazorBackRoar wants to merge 21 commits intomainfrom
codex/ty-scope-nexus-20260218

Conversation

@RazorBackRoar
Copy link
Owner

Description

Scope Ty analysis to Nexus product code and allow the optional razorcore.threading integration import.
This removes false-positive type diagnostics while preserving standalone fallback behavior.

Implementation Details

  • Added [tool.ty.src] excludes for .agent/** and .shared/** in pyproject.toml.
  • Added [tool.ty.analysis] allowed-unresolved-imports = ["razorcore.threading"].
  • No functional runtime behavior changed.

Testing Instructions

  • Run ty check in the Nexus repo.
  • Verify Ty passes without diagnostics from skill folders or optional import resolution.

Example commands:

cd /Users/home/Workspace/Apps/Nexus
ty check

Related Issues

  • N/A

Checklist

  • Tests added or updated
  • Documentation updated (README, docstrings, etc.)
  • Linter/formatter passed (e.g., ruff, black, isort)
  • No breaking changes introduced (if this is a patch)

Move Ruff config authority to Apps/ruff.toml with app-local extend file, remove duplicated pyproject Ruff blocks, and add CI guard preventing [tool.ruff] reintroduction.

Also includes formatting cleanup required for ruff format --check.
Fetch shared Ruff config from razorcore so app-local ruff.toml extend=../ruff.toml resolves in standalone GitHub Actions checkouts.
Materialize ../ruff.toml from repo-local ruff.ci.toml so app-local ruff.toml extends resolve in standalone CI without cross-repo fetches.
Create the expected 3.13 site-packages paths before ty check so strict type checking works on GitHub macOS runners with workspace-pinned ty config.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant