Maciej Urbańczyk

Interesting concept. Maybe it would be enough to add a flag which would specify whether a given schema should be parsed/formatted or not. We could extend my proposal to define...

@jmenning-solace Could you create issue about (as you described it) `format binding`? It's very interesting idea and we should not forget it :)

@jmenning-solace > my concern is this would create valid AsyncAPI documents that are invalid JSON documents. $ref is defined within JSON schema as a reference to another JSON schema, not...

@damaru-inc > I tried your example, and it does work. My concern here isn't so much with your proposal, but with the fact that at least our parser-js treats $ref...

@TamimiGitHub Hi! You have error, because you try pass the non JSON as argument to the `$RefParser.dereference` function what isn't supported. The root object for `dereference` must be JSON. What...

The described proposal/problem itself is related to my proposal, which I extended to use references to nested non-JSON schema objects - [Proposal to allow defining schema format other than default...

Still valid. @derberg Could you remove `stale` label?

@lindhe Hello! Thanks for that issue. I guess that you mean that kind of template, am I right?  That templates are copied from this place https://github.com/asyncapi/spec/tree/master/examples so better would...

@lindhe Yeah, you're right 😅 I forgot how exactly it works (I didn't implement that part). > Should that link lead to the other repo then? Yes, it should take...

@thake Thanks for that comment! Interesting idea, because then we can easily validate duplication of servers in groups local/provided and remote/used. However I think that people will have problem with...