Skip to content

docs: scope dataclass ban + document strict-per-module mechanism #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ak2k merged 2 commits into from
Oct 4, 2026
Merged

docs: scope dataclass ban + document strict-per-module mechanism #1

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1347540
docs: scope the dataclass ban + document strict-per-module mechanism
ak2k Jun 5, 2026
0ec7d78
Merge remote-tracking branch 'origin/main' into pr1-update
ak2k Oct 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -170,6 +170,13 @@ in addopts; CI opts in. Heavy native deps (`nodriver`, `camoufox`) belong in a
`[project.optional-dependencies]` `browser` extra so the core install stays
wheel-light — CI still builds the extra.

**Strict-per-module mechanism.** "standard + strict per-module on public API"
means: `typeCheckingMode = "standard"` globally (so untyped scraping libs don't
drown you) + a `# pyright: strict` file-header on each pure-logic / typed-core
module. Keep untrusted-parsing boundary modules (`json.loads -> object`
juggling) in standard mode — strict fights them and the Pydantic boundary type
validates the output anyway. TS-grade rigor on the core, tolerance at the edges.

### Profile C — Single-file script

Skip the template. PEP 723 inline header:
Expand Down
Loading