Fix GAP-33 spec-md parse error#36
Merged
Merged
Conversation
The spec-md parser requires a blank line between paragraph text and unordered list items. Without it, the parser expects whitespace but finds `-` at the start of line 351. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
magicmark
force-pushed
the
fix/gap-33-build-error
branch
from
b21435f to
946f174
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Expected [ \t] but "-" foundat line 351Test plan
npm run buildpasses locally🤖 Generated with Claude Code