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
support optional leading slash in fully qualified names #75
Comments
The client library currently supports the following resource identifiers.
If we want to support a missing forward-slash for fully qualified names, how does the API differentiate between Does it only support that the missing forward slash for actions within packages? |
This is the backend change that was implemented for reference in the cli https://github.com/apache/incubator-openwhisk/pull/2424/files Three parts: unambiguous hence can drop leading slash. |
the leading slash in a fully qualified name is optional but appears to break the library here if it's not specified.
for reference, see: apache/openwhisk#2328
The text was updated successfully, but these errors were encountered: