Fran Méndez
Fran Méndez
@joerg-walter-de thanks for the feedback. Let me go point by point: > There should be no our. We design an API. When we implement it we may implement for example...
Our Reference Object should be no different than JSON Schema one. My only concern is that we'd have to also upgrade to Draft 2019-09 but that's something we'd have to...
Same problem exists with the `summary` and `description` fields. A description that is best suited for "clients" doesn't fit well when documenting your "application". It's a mess. And it's all...
Side comment: really cool to see my fellow Spanish devs contributing to AsyncAPI 🙌
Folks, on #806 I decided to define the `channel` field in the Operation Object as a Reference Object. This way: ```yaml operations: sendUserSignedUp: action: send channel: $ref: '#/channels/userSignedUp' ``` Please...
> Do you mean some editors understand an AsyncAPI document (yaml) containing the $ref? I'm asking because I'm a bit confused., not saying this is not happening. IDEs with JSON...
> I am not sure how can put restrictions on requests and responses in publish/subscribe mode? Could you please provide your input? I'm not sure what you mean here. Are...
I think this PR can be removed in favor of #777?
> @fmvilas this change is for 2.x branch, the #777 is for 3.x branch. Assuming we don't know exactly how soon the 2.x branch of the spec goes away and...