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
Thank you for very much @inclyc for this fantastic project!
Is your feature request related to a problem? Please describe.
Recently I noticed issue 525 since I had a similar problem. My Nix code shows a lot of sema-def-not-used which sometimes is an issue and sometimes it is deliberate:
It would be handy to add a dictionary with all definitions (keys) and with severity (value) that could be changed by a user.
Describe alternatives you've considered
Warning sema-def-not-used seems to be the only warning that in some cases is wrong and therefore the easiest solution would be to change severity from warning to informational (blue squiggly line). That means forgotten bindings would be easy to locate within the code but wouldn't be too glaring.
The text was updated successfully, but these errors were encountered:
Fantastic, I've just upgraded and I have it.
Thank you!
Looking at the commit, I can see that the severity is Hint. I think Info would be a better option since Info doesn't show up in warnings / as an amber dot in the file browser but it still adds a squiggly line under the variable.
Before I upgraded to 2.2.2 sema-def-not-used helped me to realise why one of my functions doesn't work (I didn't use one of the function parameters) so it is useful.
Thank you for very much @inclyc for this fantastic project!
Is your feature request related to a problem? Please describe.
Recently I noticed issue 525 since I had a similar problem. My Nix code shows a lot of
sema-def-not-used
which sometimes is an issue and sometimes it is deliberate:Describe the solution you'd like
It would be handy to add a dictionary with all definitions (keys) and with severity (value) that could be changed by a user.
Describe alternatives you've considered
Warning
sema-def-not-used
seems to be the only warning that in some cases is wrong and therefore the easiest solution would be to change severity from warning to informational (blue squiggly line). That means forgotten bindings would be easy to locate within the code but wouldn't be too glaring.The text was updated successfully, but these errors were encountered: