Skip to content
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

AsyncAPI spec - ambiguity in wording around Specification Extensions #1663

Closed
char0n opened this issue Jun 27, 2022 · 3 comments
Closed

AsyncAPI spec - ambiguity in wording around Specification Extensions #1663

char0n opened this issue Jun 27, 2022 · 3 comments
Assignees
Labels

Comments

@char0n
Copy link
Member

char0n commented Jun 27, 2022

This ambiguity prevents using native browser search capabilities. Goal of this issue is to produce a PR against AsyncAPI spec to remedy the situation.

  • may be extended vs can be extended
  • RequIred vs REQUIRED

https://github.com/asyncapi/bindings/tree/master/mqtt#server-binding-object

  • typo in persistent
@char0n char0n self-assigned this Jun 27, 2022
@char0n char0n added enhancement New feature or request ApiDOM AsyncAPI 2.x labels Jun 27, 2022
char0n added a commit to char0n/spec that referenced this issue Jul 5, 2022
@char0n
Copy link
Member Author

char0n commented Jul 5, 2022

asyncapi/spec#818

@char0n
Copy link
Member Author

char0n commented Jul 5, 2022

asyncapi/bindings#139

@char0n
Copy link
Member Author

char0n commented Jul 5, 2022

Lifecycle of these two PRs is tracked in https://github.com/swagger-api/oss-planning/issues/560

@char0n char0n closed this as completed Jul 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant