Clarify custom mode YAML parsing limitations #237
Closed
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.
This commit updates the documentation for manually editing custom modes (
.roomodes) to improve clarity and help users avoid some parsing pitfalls discovered during real-world testing.The key changes include:
&,*) are not supported by the parser.fileRegexpermission syntax is unstable and recommending a simpler, more reliable alternative (groups: [read, edit]).These updates provide an accurate reflection of the YAML parser's behavior and will lead to a better user experience.
Important
Updates documentation to clarify YAML parsing limitations for custom modes, including unsupported features and recommended practices.
custom-modes.mdx.&,*).fileRegexsyntax due to instability.groups: [read, edit]permissions.This description was created by
for 4e1e043. You can customize this summary. It will automatically update as commits are pushed.