You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The language server should provide a code action to allow developers to disable a rule in .regal/config.yaml via the "Quick fix" menu provided where the error is reported.
If no .regal/config.yaml is found, we should create one.
The text was updated successfully, but these errors were encountered:
I looked into this briefly last night, and the big challenge here is preserving user comments. These are quite common in .regal/config.yaml files, and they should be! That's a great way to document why some rule is disabled, or configured the way it is. Wiping these as part of a marshalling roundtrip would be terrible, so we'll need to make this a custom process... which makes it non-trivial.
Honestly, it's probably easier to just skip parsing altogether, just grep for <category>: and then insert text straight into the document. I mean, just look at this.
Yeah, I looked at that but didn’t find a good example like that! It’s worth a shot, although it’s not 100% lossless AFAICS, but perhaps it’s fine to mess a little with whitespace.
The language server should provide a code action to allow developers to disable a rule in
.regal/config.yaml
via the "Quick fix" menu provided where the error is reported.If no
.regal/config.yaml
is found, we should create one.The text was updated successfully, but these errors were encountered: