-
-
Notifications
You must be signed in to change notification settings - Fork 106
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
fix: upgrade @asyncapi/specs #423
Merged
jonaslagoni
merged 23 commits into
asyncapi:master
from
jonaslagoni:feature/update_spec_json_schema
Sep 13, 2022
Merged
Changes from all commits
Commits
Show all changes
23 commits
Select commit
Hold shift + click to select a range
a865a0c
Prepared for new spec repo.
jonaslagoni 15949e4
Prepared for new spec repo.
jonaslagoni 12c8fb1
Added file extension
jonaslagoni 09a050a
Merge branch 'master' into feature/update_spec_json_schema
jonaslagoni d7cfbf4
Update package.json
jonaslagoni 973e9b2
Merge branch 'master' into feature/update_spec_json_schema
jonaslagoni 4842a82
Updated dependency
jonaslagoni 8af4a34
WIP schema format parser
jonaslagoni 9d74fb4
Merge branch 'master' into feature/update_spec_json_schema
smoya bcb5216
removed bundled json schema
jonaslagoni 43ad46c
Merge branch 'master' into feature/update_spec_json_schema
jonaslagoni d22ad29
removed draft 4 meta schema
jonaslagoni 7dcb8a9
Updated with new spec version
jonaslagoni b3361a0
Merge branch 'master' into feature/update_spec_json_schema
jonaslagoni acdd428
updated to new package
jonaslagoni fc1c54c
Merge branch 'master-main' into feature/update_spec_json_schema
jonaslagoni 89c6db0
updated packagelock
jonaslagoni 4819866
updated package
jonaslagoni 67a25e3
Update lib/asyncapiSchemaFormatParser.js
jonaslagoni 244f0f6
Merge branch 'master' into feature/update_spec_json_schema
jonaslagoni 933058d
Merge branch 'master' into feature/update_spec_json_schema
jonaslagoni c83b53d
Merge branch 'master-github-upstream' into feature/update_spec_json_s…
jonaslagoni d5ef367
update package-lock
jonaslagoni File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
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.
why can't we grab it from
@asyncapi/specs
instead of remote?sorry if that was answered somewhere already. Also, I do not remember really much from times when I created
asyncapiSchemaFormatParser.js
just dereferencing something in the parser from remote is going to slow down parsing, or?
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.
We are using the local one from
@asyncapi/specs
🙂It is only what the reference is called. Ajv automatically matches it with the schema inside
definitions
🙂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.
do we need http://asyncapi.com/definitions/ published before we merge?
tbh I'm not 100% sure how these $id work...to complicated for me 😄
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.
Not at all, the
$id
s when bundled together like so, do not need external access to the schemas 🙂 Because validation tools must look for the reference within before reaching externally.We don't need to expose them at all if everyone uses the bundled schemas, but say you want to use this one: https://github.com/asyncapi/spec-json-schemas/blob/master/definitions/2.4.0/asyncapi.json, it would need the schemas exposed on http://asyncapi.com/definitions/ as the schemas are not located within.
Does that make sense?