Currently, any bindings provided seem to be left out of the HTML/Markdown.
Even if we aren't doing any validation on them, it would be valuable IMO to have the HTML/Markdown include these bindings, specified as such and basically copied as-is from the schema.
This way, if you specify some bindings in your schema definition, anyone reading those API documents will be able to see those.
In the future this could be made more sophisticated, but just pushing them out in some reasonable form would add value as a start.
I would also like to see this. For the Solace template I'm writing, bindings are essential.
Yea, I agree this would be useful. Maybe we could reuse the implementation from https://github.com/asyncapi/generator/issues/136. Also since the bindings are far from stable I think this could be a suitable solution to this issue, what do you think?
馃憤 to @jonaslagoni suggestion. Seems like a suitable solution meanwhile bindings get stable.
Looks like a perfect issue for me to start with templating and having a need to understand bindings? Anyone working on it already, or can I pick it up?
I'd not work on this issue yet. Bindings specs are really unstable yet. Maybe this one is better as your next one: https://github.com/asyncapi/generator/issues/182.
sure thing, I thought about this one as an alternative temp solution was suggested, but #182 is also fine
This issue has been automatically marked as stale because it has not had recent activity :sleeping:
It will be closed in 30 days if no further activity occurs. To unstale this issue, add a comment with detailed explanation.
Thank you for your contributions :heart:
Issue moved to asyncapi/html-template #25 via ZenHub
Most helpful comment
Yea, I agree this would be useful. Maybe we could reuse the implementation from https://github.com/asyncapi/generator/issues/136. Also since the bindings are far from stable I think this could be a suitable solution to this issue, what do you think?