The Jsonnet Language Server provides IntelliSense for direct imports but not for objects created by merging imported objects.This is a common pattern in Jsonnet codebases where libraries are imported and then merged with configuration. The LSP should be able to infer that merged objects retain the same structure as the base object.
Steps to Reproduce:
- Import a Jsonnet library:
local kubeBase = (import 'kube.libsonnet');
- Merge it with configuration:
local kube = kubeBase { namespace:: 'test', ... };
- Try to use IntelliSense: Type
kube. - no autocomplete appears
- Compare with: Type
kubeBase. - autocomplete works correctly
Environment:
- Extension: Grafana Jsonnet v0.7.2
- Jsonnet Language Server version: 0.16.0
- Editor: Cursor 2.3.29
- OS: Debian GNU/Linux 12 (bookworm) on Linux 6.8.0-1030-azure (Azure Codespaces)
- Architecture: x86_64
The Jsonnet Language Server provides IntelliSense for direct imports but not for objects created by merging imported objects.This is a common pattern in Jsonnet codebases where libraries are imported and then merged with configuration. The LSP should be able to infer that merged objects retain the same structure as the base object.
Steps to Reproduce:
local kubeBase = (import 'kube.libsonnet');local kube = kubeBase { namespace:: 'test', ... };kube.- no autocomplete appearskubeBase.- autocomplete works correctlyEnvironment: