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

Enable v3 validation support #742

Closed
4 tasks done
smoya opened this issue Jul 18, 2023 · 1 comment
Closed
4 tasks done

Enable v3 validation support #742

smoya opened this issue Jul 18, 2023 · 1 comment

Comments

@smoya
Copy link
Member

smoya commented Jul 18, 2023

Relates to #641

AsyncAPI v3 is still WIP. We are in a very advanced position, however there are still blockers for early releasing something users can use.
In order to let users test AsyncAPI v3 in advance, I suggest we aim to release a beta version (as a release candidate) version of Studio with the support of the very basics: validating ASyncAPI v3 documents. That means no documentation or code generation, no Spectral rules, etc. Just JSON Schema validation. We will add all those features later progressively.

This issue aims to list and track all the work needed to make this version happen.

Scope

Studio: Enable validation only

Disable everything except the editor tab and document validation. Use ParserJS rc + JSON Schema rc.

@fmvilas fmvilas changed the title MVP for Studio supporting AsyncAPI v3 Enable v3 validation support Jul 19, 2023
@Amzani Amzani self-assigned this Jul 25, 2023
@Amzani Amzani removed their assignment Jul 25, 2023
@Amzani Amzani closed this as completed Feb 16, 2024
@github-project-automation github-project-automation bot moved this from Backlog to Done in Studio - Kanban Feb 16, 2024
Copy link

shapeit-bot bot commented Feb 16, 2024

Thanks for creating a new pitch 🥳. You can now create or link existing scopes.
You can create new scopes in two different ways:

Option 1

  1. Edit the Pitch or Bet issue
  2. Add your scope under the scope section

See this example

Option 2

  1. Create a new issue
  2. Add this keywork in the description related to #ISSUE_BET_NUMBER

See this example

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Status: No status
Development

No branches or pull requests

2 participants