An open-source freak that started his career as a tech writer. Then got into development to later become a product owner that because of being an open-source freak started working as dev comm keeper
An open-source freak that started his career as a tech writer. Then got into development to later become a product owner that because of being an open-source freak started working as dev comm keeper
Last year was fully focused on releasing AsyncAPI 2.0, so getting the spec more mature.
This year we focus on tooling. Come and join us.
Quicktype will generate just types for you, this is why we want to integrate it in generator for code templates. But it cannot really replace generator.
What is that you exactly need except of the spec? What do you want to get out of the spec?
I need the specs to describe the methods that can be sent. Each method needs to describe:
Its name.
Its fields (and their possibly deep types)
What it returns.
Free text to describe what it does.
Ideally I'd like something that can generate the full API. For example, if I have
-name:fooparameters:-name:bartype:integer-name:baztype:textreturns:-name:xtype:float-name:ytype:floatdoc:bla bla bla
It would generate, say for Java:
publicclassFooResult{privatefloatx;privatefloaty;publicFooResult(floatx,floaty){this.x=x;this.y=y;}publicfloatgetX(){returnx;}publicfloatgetY(){returny;}}publicabstractclassAbstractAPI{protectedabstractValuecall(Stringmethod,Valueparameters);/**
* bla bla bla
*/publicFooResultfoo(intbar,Stringbaz){Valuerequest=newValue();request.setInt("bar",bar);request.setString("baz",baz);Valueresult=call("foo",request);returnFooResult(result.getFloat("x"),result.getFloat("y"));}}
And then you'll just have to subclass AbstractAPI (yes, I know) and implement call and you'll get fully typed access to the entire API.
An open-source freak that started his career as a tech writer. Then got into development to later become a product owner that because of being an open-source freak started working as dev comm keeper
also, for code generation -> we released a new library for generating types/models. It can be used with our generator and also as a standalone. Long term we want to integrate it with new CLI so you can easily generate models from CLI -> github.com/asyncapi/generator-mode...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Definitely AsyncAPI -> github.com/asyncapi/asyncapi/
We have many people asking about websockets in our slack asyncapi.com/slack-invite/
Still seems thin in the language support department - only thing added since I posted this almost a year ago is node.js templates.
I did find this ticket though - github.com/asyncapi/generator/issu... - which suggests using something like quicktype.io/. So maybe I should just use quicktype?
Last year was fully focused on releasing AsyncAPI 2.0, so getting the spec more mature.
This year we focus on tooling. Come and join us.
Quicktype will generate just types for you, this is why we want to integrate it in generator for code templates. But it cannot really replace generator.
What is that you exactly need except of the spec? What do you want to get out of the spec?
I need the specs to describe the methods that can be sent. Each method needs to describe:
Ideally I'd like something that can generate the full API. For example, if I have
It would generate, say for Java:
And then you'll just have to subclass
AbstractAPI
(yes, I know) and implementcall
and you'll get fully typed access to the entire API.Hey, fyi I published some materials about WebSocket API and AsyncAPI github.com/asyncapi/spec/issues/25...
also, for code generation -> we released a new library for generating types/models. It can be used with our generator and also as a standalone. Long term we want to integrate it with new CLI so you can easily generate models from CLI -> github.com/asyncapi/generator-mode...