fix: avoid error caused by line_range type: null in discussion #107
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.
Motivation
While testing the mr_discussions tool in MCP with Cursor, I encountered the following error for certain MRs:
Looking at the underlying API response, the issue was caused by a line_range block that did not include a type field. For example:
In this case, end.type was not just one of new/old/expandable but null.
Changes
Updated the zod schema for line_range to use the common LineRangeSchema, which already had
type
as nullableTesting
Confirmed that running the mr_discussions tool against the affected MR now works as expected using the following mcp.json configuration:
Full JSON of erroring response