-
Notifications
You must be signed in to change notification settings - Fork 1
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
Subcommands for working with multi-dimensional values #42
Comments
The dot notation idea came up before (might've been you, can't find the issue), but option names can contain dots. |
I think the
|
Are you guys open to a PR for |
@aaemnnosttv Yes, these might come in handy, and this specific approach is the safest one we are aware of. |
E.g.
Returns
bar
Updates
bar
tobaz
Ideally it would be great to be able to use dot notation using the normal functions, but option names could contain dots or really any other character that could be used to separate hierarchy.
e.g.
Returns
bar
This same idea could be applied to just about all
get
set
commands, for meta, transient, etc.The text was updated successfully, but these errors were encountered: