You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Parser v2.0 is moving forward, and it SHOULD ideally be released way before Spec v3.0, so people can familiarize with the new API but also have a smooth transition from spec v2 to v3 in terms of tooling (no breaking change).
As Parser v2.0 implements this new Intent-Driven API, it is a requirement to build the final v1.0.0 version of the API ASAP.
This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.
There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.
Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.
Reason/Context
Parser v2.0 is moving forward, and it SHOULD ideally be released way before Spec v3.0, so people can familiarize with the new API but also have a smooth transition from spec v2 to v3 in terms of tooling (no breaking change).
As Parser v2.0 implements this new Intent-Driven API, it is a requirement to build the final
v1.0.0
version of the API ASAP.Description
next-major
branch CODE OWNERS https://github.com/asyncapi/parser-js/blob/next-major/CODEOWNERScc @magicmatatjahu @jonaslagoni @fmvilas @derberg
The text was updated successfully, but these errors were encountered: