-
Notifications
You must be signed in to change notification settings - Fork 1
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
Align with OneSDK@3 #107
Draft
freaz
wants to merge
4
commits into
main
Choose a base branch
from
feat/update_provider_json
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Align with OneSDK@3 #107
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
freaz
force-pushed
the
feat/update_provider_json
branch
from
July 18, 2023 19:30
1cc6728
to
4dd3826
Compare
freaz
changed the title
Update provider json to align with OneSDK@3
Update provider.json to align with OneSDK@3
Jul 18, 2023
freaz
force-pushed
the
feat/update_provider_json
branch
from
July 19, 2023 07:44
4dd3826
to
e79149c
Compare
freaz
force-pushed
the
feat/update_provider_json
branch
from
July 19, 2023 07:57
e79149c
to
7542b87
Compare
freaz
commented
Jul 19, 2023
Comment on lines
58
to
65
"bodyType": { | ||
"$id": "ApiKeyBodyType", | ||
"description": "Body type to inject security value to.", | ||
"enum": [ | ||
"json" | ||
], | ||
"type": "string" | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some dark magic happening here. Compared to ApiKeyPlacement
if I use $ref
on the field, it will be still created in place but with id and ref, so there is circular reference. And I am unable to convince typescript-json-schema
library to generate ApiKeyBodyType
in definitions. 🤷
freaz
changed the title
Update provider.json to align with OneSDK@3
Align with OneSDK@3
Jul 19, 2023
freaz
force-pushed
the
feat/update_provider_json
branch
from
July 19, 2023 09:22
9208fd0
to
d9743f5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This needs to be major release of AST.
For changes see CHANGELOG
Todo
ApiKeySecurityScheme
and havebodyType
required fortype: "body"
.Fighting typescript-json-schema lib
Motivation and Context
Makes
assertProviderJson
to behave as expectedTypes of changes
Checklist: