-
Notifications
You must be signed in to change notification settings - Fork 168
Harmonize positional vs keyword namespace: args #312
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Summary of current signatures wrt. name & namespace:
😱 😖 |
What do you think about requiring keywords for all identifying parameters? E.g. instead of
Instead we do
For myself, I think it would be ideal if we required keywords for all parameters for the get/update/patch/etc. |
I don't want to break comaptibility, especially as this would affect almost every call. See also #332 that proposes a new hash-only interface. EDIT: looking at #391... |
In some method we take namespace as optional positional arg, in some as optional keyword
namespace:
arg. This is error-prone, and doesn't scale as we want to add more optional args. (It'd be especially awkward if you'd need to pass dummy nil namespace when dealing with a non-namespaced entity such as nodes...)Long-term I'd like to support keyword
namespace:
everywhere, initially still supporting positional where needed for compatibility, eventually deprecating positional.The text was updated successfully, but these errors were encountered: