Vladimír Gorej
Vladimír Gorej
Given we've discontinued effort with [2.4.1](https://github.com/asyncapi/spec/issues/821) release and are going directly for [2.5.0](https://github.com/asyncapi/spec/issues/830), this PR needs to be send against next-spec and the title needs to changeto `feat: allow re-usability...
Right, I'll do it right after https://github.com/asyncapi/spec/pull/831 is merged. I guess it would require re-review of all code owners.
Base branch changed for `next-spec`.
/ready-to-merge
Changed title from `fix: allow re-usability of Server Variable Objects` to `feat: allow re-usability of Server Variable Objects`. Can I ask somebody to to remove `do-not-merge` label or merge this...
HI @magicmatatjahu, Very quickly couple of points I can think of: --- The `Reference Object` comes originally from OpenAPI spec and as far as I understand is was introduced to...
Hi @magicmatatjahu, > I had in mind that when I wrote issue, but in my opinion, saying which things should be reusable and which should not only causes misunderstanding of...
> More details in JSON Schema -> URL shoudl be of uri format so RFC3986. You want it explicit in the spec markdown file too, right? Yep, I expect the...
Closing as https://github.com/asyncapi/spec/pull/782 has been merged to master as editorial change.
> @char0n Hello! We only allow the names of the servers (and don't reference) for simple reason Right, I was specifically referring to the usage with in `Channel Item Object`.`server`...