Sergio Moya

Can we solve this with a `pattern` field on the JSON Schema `Reference Object` ?

Otherwise, AJV should throw an error (`MissingRefError`) anyway. See this example I built: https://onecompiler.com/nodejs/3y9pgk7py

Issue is resolved in v2 ParserJS - now in https://github.com/asyncapi/parser-js/tree/next-major branch thanks to Spectral. Pending to add a test. cc @magicmatatjahu

> About all these docs and explanations for contributors, it would be amazing to have your input @alequetzalli 🙂. That would be awesome!🤞 I have to say that we had...

> * how long will it take to deprecate methods? If breaking change occurs, are we planning to keep old methods for one major version and then remove them? This...

> yes yes yes, consistency across parsers would be awesome, would make many things much easier long term. I'm just not sure if it has to be super perfect now...

@felixjung Your point is not only very valid and useful. It is also in the direction of some of the discussions people are having in https://github.com/asyncapi/spec/issues/618#issuecomment-1036490698. So I encourage you...

For the reference, https://github.com/asyncapi/parser-js/pull/453 it is considered now the implementation to follow of the Parser-API

This task is under development, and all PR's should target [next-major](https://github.com/asyncapi/parser-js/tree/next-major) branch, where also [Migrate project to TypeScript](https://github.com/asyncapi/parser-js/issues/482) is happening.

No way `github-actions`!! This is in development actually! https://github.com/asyncapi/parser-js/issues/481