This is another entry on my bi-weekly update about the AsyncAPI Spec and parsers. This time with a bit of delay.
Note This is not an official AsyncAPI update but a personal summary I volunteer to do.
What do I mean by AsyncAPI Spec and parsers update?. As most of the work around the AsyncAPI Spec is not only related to https://github.com/asyncapi/spec, each update will include the most significant recent activity from the following repositories:
Feel free to ask me to include any other repository if you consider it makes sense. Also, in case you want to help me with these updates :)
2.4 release is happening this month!
The following changes are confirmed (some pending to be merged):
- Make Server Variables Object available as reusable objects under the Component object
- feat: add security at the operation level
- Add support for messageId
- Unable to reuse Server Objects defined in Components.servers field
We are still on time to add last minute changes into this version, so please feel free to suggest any RFC you think it should be included on 2.4!
Operations at components level RFC
Allow grouping servers RFC
One new Spec
3.0 live meetings has been held 📹.
📅 The next one is going to happen on 16:00 UTC Wednesday April 13 2022. Do not miss it!
v2.13.2 got released! 🎉
It includes the fix: add v2 suffix to Go module](https://github.com/asyncapi/spec-json-schemas/pull/126) by Sergio Moya.
The rewrite to Typescript is moving forward!
As mentioned in the previous bi-weekly update, this is not only a migration to TypeScript, but also a complete rewrite of the
parser-js, adopting finally the Intent-driven API of Parser-API, which a POC was created a few weeks ago as well (See this PR).
v1.0.0-alpha.2 is out, now including all changes introduced on latest work on
Parser-API contains now all changes introduced on latest work on
parser-js, as mentioned in Update API according to the latest implementation in Parser-JS by Sergio Moya.