Skip to content
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

Leafref tab completion: "present" vs. "all possible" #8

Open
jktjkt opened this issue Dec 19, 2023 · 0 comments
Open

Leafref tab completion: "present" vs. "all possible" #8

jktjkt opened this issue Dec 19, 2023 · 0 comments

Comments

@jktjkt
Copy link
Contributor

jktjkt commented Dec 19, 2023

With the following model where the second list's keys reference the first list:

  +--rw channel-plan
  |  +--rw channel* [name]
  |     +--rw name               string
  |     +--rw lower-frequency    dwdm-frequency-mhz
  |     +--rw upper-frequency    dwdm-frequency-mhz
  +--rw media-channels* [channel]
  |  +--rw channel        -> /channel-plan/channel/name
  |  +--rw description?   string
...

The tab-completion below media-channels currently offers only the already existing keys. That makes sense, but it would be nice to also have an option of tab-completing against all possible keys, which is exactly the set of all existing keys in the first list. This is of course tricky to do in the backend, as well as tricky to export this feature to the user (shift-tab, maybe? or a global togglable flag?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant