Debug: Log missing line numbers in ast-grep output #7
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.
Problem
PR x shows all lint warnings with line number 1:
This is happening because
issue.range?.start?.lineis undefined in the ast-grep JSON output in CI, causing all line numbers to default to 1 (see shared.ts:94).Solution
This PR adds debug logging to understand what the actual JSON structure looks like when range data is missing.
Next Steps
Once we see the logs, we can:
To Test
Use this branch temporarily in a workflow to see the putout