-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
Corresponding code actions for diagnostics #39
Comments
Note that we can get back diagnostics from Code Actions requests. This would make it easier to implement without duplicate checking codes.
These should be left as-is and let user check what is happening.
These could occur as false-positives during editing. Delete actions would hurt by accidental application. As a reference, |
I crossed these out now
I think it makes sense for rust to do that due to the impurities, but for nix there shouldn't be a reason to have dead code |
This fix could be implemented together with string rewriting under the name
|
@oxalica I'm interested in trying to implement the Also happy to chat on Matrix, if that's your thing. |
You can follow other PRs like #41. For string content, there are some helper functions for unescaping in nil/crates/syntax/src/semantic.rs Line 71 in 1c122ae
I attached my Matrix address in my profile page. But I might not be quite responsive recently. |
List from
DiagnosticKind
SyntaxErrorLowering
InvalidDynamicDuplicatedKeyDuplicatedParamMergePlainRecAttrsetMergeRecAttrsetName resolution
Liveness
The text was updated successfully, but these errors were encountered: