-
Updated
Oct 6, 2020 - JavaScript
asyncapi
Here are 52 public repositories matching this topic...
Reason/Context
With the current API document for the generator it does not state you have access to the parsed AsyncAPIDocument on asyncapi and the AsyncAPI file on originalAsyncAPI.
Description
We need to add jsdoc to the following lines:
https://github.com/asyncapi/generator/blob/4c8dd9de88c701ccf1af
-
Updated
Oct 8, 2019 - JavaScript
-
Updated
Oct 9, 2020 - Java
-
Updated
Oct 8, 2020 - TypeScript
Add HTTP Bindings
HTTP is a popular format for async messaging (webooks).
We should provide
- classes for HTTP bindings,
- documentation on how to use HTTP bindings
https://github.com/asyncapi/bindings/tree/master/http
Bindings are currently usable by creating a filter which adds the binding.
e.g.
services.AddAsyncApiSchemaGeneration(options =>
{
options.ChannelItemFilters.Add(new MyAmq-
Updated
Oct 9, 2020 - Shell
-
Updated
Oct 2, 2020 - JavaScript
-
Updated
Oct 9, 2020 - Java
-
Updated
Oct 2, 2020 - JavaScript
-
Updated
Sep 26, 2020
-
Updated
Oct 8, 2020 - JavaScript
-
Updated
Oct 7, 2020 - JavaScript
-
Updated
Oct 3, 2020 - JavaScript
-
Updated
Jul 2, 2019 - Go
-
Updated
Jul 20, 2020 - Go
-
Updated
Oct 1, 2020 - JavaScript
@maxs commented on Thu Mar 12 2020
In the folowing example description field won't be rendered in resulting output because it is not taken from the parameter toy but the schema. This means, to have description rendered, we would have to put description under schema block which is not intended behavior.
components:
p-
Updated
Oct 9, 2020 - Ruby
-
Updated
Oct 1, 2020 - JavaScript
-
Updated
Sep 12, 2020 - C#
-
Updated
Oct 1, 2020 - JavaScript
Improve this page
Add a description, image, and links to the asyncapi topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the asyncapi topic, visit your repo's landing page and select "manage topics."
I had opened an issue in the Shins project along these lines, but felt it might be better(?) considered here. Mermade/shins#53
To state the scenario from that issue:
Once a user is logged into our site, I'd like to be able to inject a user's API key dynamically into the API calls within the documentation. I'm using Widdershins to generate the base docs from OpenAPISp