docs: correct stale &+N relative-offset parsing TODO claims (#287)#306
Conversation
AGENTS.md and GOTCHAS.md both stated that magic-file &+N/&-N relative-offset parsing was "still TODO". Parsing has been implemented for some time and is exercised by parse_offset_relative tests in src/parser/grammar/tests/mod.rs (covers &0, &4, &+4, &-4, &0x10, &-0x10; bare & rejected). - AGENTS.md Offset Specifications: replace the TODO clause with a statement that &N/&+N/&-N parsing is implemented, including hex forms, and point to the parse-side test module. - GOTCHAS.md S3.11: replace the canonical fail-fast example (which used &+N as the unsupported syntax) with an unquoted $VAR string value on a non-string-family type, which remains a real parse failure per S3.6. Pure documentation. No code changes. Closes #287 Signed-off-by: UncleSp1d3r <unclesp1d3r@evilbitlabs.io>
Merge ProtectionsYour pull request matches the following merge protections and will not be merged until they are valid. 🟢 Enforce conventional commitWonderful, this rule succeeded.Require conventional commit format per https://www.conventionalcommits.org/en/v1.0.0/. Skipped for bots.
🟢 Full CI must passWonderful, this rule succeeded.All CI checks must pass. Release-plz PRs are exempt because they only bump versions and changelogs (code was already tested on main), and GITHUB_TOKEN-triggered force-pushes suppress CI.
🟢 Do not merge outdated PRsWonderful, this rule succeeded.Make sure PRs are within 10 commits of the base branch before merging
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
Summary by CodeRabbitDocumentation
WalkthroughThis PR updates documentation in ChangesDocumentation: Relative offset parsing completion
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Suggested labels
Poem
🚥 Pre-merge checks | ✅ 10✅ Passed checks (10 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Warning Review ran into problems🔥 ProblemsThese MCP integrations need to be re-authenticated in the Integrations settings: Linear, Notion Comment |
There was a problem hiding this comment.
Pull request overview
Documentation-only cleanup that removes stale TODO claims about magic-file &+N / &-N relative-offset parsing, which has been implemented and tested. Updates the canonical fail-fast example in GOTCHAS.md to a still-unsupported syntax case.
Changes:
- AGENTS.md: corrects "Offset Specifications" to state
&N/&+N/&-Nparsing is implemented (decimal + hex; bare&rejected), pointing atparse_offset_relativefor coverage. - GOTCHAS.md S3.11: replaces the stale
&+Nexample with an unquoted$VARvalue on a non-string-family type as the canonical fail-fast trigger.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| AGENTS.md | Replaces TODO claim with accurate description of implemented relative-offset parsing. |
| GOTCHAS.md | Updates fail-fast example to a still-valid unsupported-syntax case. |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Summary
&N/&+N/&-Nparsing is implemented (decimal and0xhex forms; bare&rejected) and points atparse_offset_relativeinsrc/parser/grammar/tests/mod.rsfor parse-side coverage.parse_text_magic_fileis Fail-Fast) to use an unquoted$VARstring value on a non-string-family type as the canonical fail-fast example, since&+Nis no longer an unsupported-syntax case per S3.6.Test Plan
rg -n '&\+N' AGENTS.md GOTCHAS.mdreturns only the corrected line on AGENTS.md:245 and the still-accurate evaluator-semantics line on AGENTS.md:216.parse_offset_relativeinsrc/parser/grammar/tests/mod.rsalready verifies the claim — no new tests needed.Closes #287