fix: Remove trailing comma in the rust-analyzer configuration for linked projects #5087
Conversation
This file contains 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 commit fixes a JSON syntax issue in the rust-analyzer configuration file. The trailing comma after the last item in the "rust-analyzer.linkedProjects" list has been removed to ensure the file adheres to the JSON standard. Without this fix, tools processing the JSON file could encounter errors.
|
Himess
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR fixes a JSON syntax issue in the rust-analyzer configuration file. The trailing comma after the last item in the
"rust-analyzer.linkedProjects"list has been removed to comply with the JSON standard.Drive-by changes
None.
Related issues
None.
Backward compatibility
Yes, these changes are backward compatible as they only fix a JSON formatting issue and do not impact functionality.
Testing
Manual validation was performed to ensure the JSON file is now valid and properly handled by tools.