-
-
Notifications
You must be signed in to change notification settings - Fork 202
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
Additional features #722
base: main
Are you sure you want to change the base?
Additional features #722
Conversation
…es not have description
…e 'x-code-tag' property on the operation
This PR will have to be split up into one-per-significant-change so that our changelog generation & versioning can function properly—that will also make it easier to figure out if some of these fixes/features are duplicates of other PRs. That's not to say that anyone involved so far needs to do this, just that it will have to happen before the changes merge. I need to update the contributing guidelines to make that more clear, right now it just vaguely mentions conventional commits 😞 |
@dbanty i will create separate PR for the features i worked on - but not for the features i pulled from other forks |
I added the additional features i needed from other forks along with one more feature that i needed into this fork
x-response-type
property (can be one of: auto, success, failure)x-focus-path
to create sync_focused/asincio_focused functions that target directly a specific path inside the parsed responsePath to this optional template can be controlled independantly, and template can be linked per endpoint using
x-utility-functions-template
attribute