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
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
nixd is able to jump to NixOS option declarations from the point they're set but not the points where their value is read using the config argument.
Describe the solution you'd like
A clear and concise description of what you want to happen.
It'd be great if nixd could also jump to option declarations from config.option.name.here
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
-
Additional context
Add any other context or screenshots about the feature request here.
It's common for config attributes to be put into another variable via let:
nixd should be able to resolve this redirection and jump to the declaration of options.foo.bar.baz when attempting to jump to the declaration of cfg.baz.
The text was updated successfully, but these errors were encountered:
A type system in lsp is cool, but there is indeed two different mechanism we need to have if we choose to implement all these in lsp instead of a new language -- the type system for nixos modules, and the type system for normal nix codes. They are very different but intuitively can be fused into a single one, but I don't know how to fuse them yet
I don't think proper typing is going to happen in Nix any time soon. If work were to start now, I'd expect it to be usable no sooner than a decade later.
I also don't understand how a type system would be relevant here as this should be able to use a similar code-path to the current jump to option declaration; regardless of its type.
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
nixd is able to jump to NixOS option declarations from the point they're set but not the points where their value is read using the
config
argument.Describe the solution you'd like
A clear and concise description of what you want to happen.
It'd be great if nixd could also jump to option declarations from
config.option.name.here
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
-
Additional context
Add any other context or screenshots about the feature request here.
It's common for
config
attributes to be put into another variable vialet
:nixd should be able to resolve this redirection and jump to the declaration of
options.foo.bar.baz
when attempting to jump to the declaration ofcfg.baz
.The text was updated successfully, but these errors were encountered: