-
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
Allow using operationId
to find the handler
#2
Comments
I did not know about the "operationId", and it is an interesting idea. Must think how to organize operations subsystem. |
This is a greate idea. As a generale purpose, it would be greate to only remove keys from the spec if its name starts with '$'. |
Resolved
|
add_operations renamed to add |
Wow, awesome job, @aamalev! Would you like me to close this issue or is there any reason you kept it open? |
Need to document this functionality |
I'd much rather have unique IDs in the existing
operationId
value for each handler, and thenhandlers_module='mymodule.handlers'
to have it automaticallygetattr(mymodule.handlers, yaml['operationId'])
the handlers from there.The text was updated successfully, but these errors were encountered: