-
Notifications
You must be signed in to change notification settings - Fork 13
chore(fsharp): align npm grammar with cargo at v0.3.0 #1165
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.
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
carlos-alm
merged 2 commits into
fix/1114-fsharp-signature-grammar
from
fix/1161-fsharp-grammar-skew
May 19, 2026
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because the npm registry has no 0.3.0 release, the tarball URL is the right choice here. Worth noting: unlike
^0.x.ysemver ranges,npm updatewill never touch this entry — upgrading to a future release (e.g. 0.4.0) requires a manual URL edit in bothpackage.jsonandpackage-lock.json. A short comment inpackage.jsonwould help future maintainers know why the tarball form was chosen instead of a registry reference.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed — added a docblock to
src/extractors/fsharp.tsexplaining (a) why the tarball form is used (no v0.3.0 on npm), (b) that the cargo crate uses the same version, and (c) that upgrading requires a manual URL edit in bothpackage.jsonandpackage-lock.jsonbecausenpm updatewon't touch this entry. Put it in the extractor docblock rather thanpackage.jsonsince pure JSON doesn't support comments and a_commentfield would be non-standard for this repo.