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?)
With the following model where the second list's keys reference the first list:
The tab-completion below
media-channelscurrently 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?)