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
If I have an attrset with a newline after the { in a position that admits functions, this is scoped as punctuation.definition.attrset-or-function.nix. In this context, if the first key is an antiquotation, it flags this as a syntax error. Besides being an incorrect error, this can cause the rest of the file to tokenize incorrectly as well.
As an example, see lib/generators.nix in nixpkgs. This also highlights incorrectly in GitHub of course. Sample extract:
In this example, the rest of the line ends up being treated as inside a double-quoted string, and so the rest of the file is highlighted incorrectly.
This particular issue is actually something I fixed in my vscode-nix fork a year ago, see lilyball/vscode-nix@2a7db0f, but I'm not in a position to port this to vscode-nix-ide or open any PRs at the moment.
The text was updated successfully, but these errors were encountered:
If I have an attrset with a newline after the
{
in a position that admits functions, this is scoped aspunctuation.definition.attrset-or-function.nix
. In this context, if the first key is an antiquotation, it flags this as a syntax error. Besides being an incorrect error, this can cause the rest of the file to tokenize incorrectly as well.As an example, see
lib/generators.nix
in nixpkgs. This also highlights incorrectly in GitHub of course. Sample extract:In this example, the rest of the line ends up being treated as inside a double-quoted string, and so the rest of the file is highlighted incorrectly.
This particular issue is actually something I fixed in my
vscode-nix
fork a year ago, see lilyball/vscode-nix@2a7db0f, but I'm not in a position to port this tovscode-nix-ide
or open any PRs at the moment.The text was updated successfully, but these errors were encountered: