-
Notifications
You must be signed in to change notification settings - Fork 9
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
Consider adding wildcard support for unregistering capabilities #61
Labels
Comments
16 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
The API for unregistering capabilities does not support wildcards, which seems to be intentional according to the method's TypeDoc. Thus, to unregister multiple capabilities, the application first has to look up matching capabilities and then unregister them, one by one, using their ids.
The method's TypeDoc says:
If given a qualifier in the filter, wildcards, if any, are not interpreted as wildcards, but as exact values instead.
What was the reason for not supporting wildcards? This restriction is very tedious and error-prone and also leads to potentially many API calls.
Describe the solution you'd like
It would be convenient to support wildcards for unregistering capabilities.
The text was updated successfully, but these errors were encountered: