-
-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Doesn't work for Hello world example from AsyncAPI #1488
Comments
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request. |
Strangely you need to pass title to payload: asyncapi: 3.0.0
info:
title: Hello world application
version: '0.1.0'
channels:
hello:
address: 'hello'
messages:
sayHelloMessage: # it doesn't read message name from here
payload:
title: SayHelloMessage # so you need to put it here
type: string
pattern: '^hello .+$'
operations:
receiveHello:
action: 'receive'
channel:
$ref: '#/channels/hello' But now I get:
|
Hi @slavaGanzin The |
I cant transfer it as I am not maintainer of Cli 🙂 |
in short @slavaGanzin, it's because Modelina only generate payload representations, not messages. I.e. it is not generating anything for python, unless string can be rendered someway.
|
@Amzani @jonaslagoni I know that it is a Modellina responsibility. But I shouldn't - I was advertised that the generator would generate a model, but it didn't. And the problem is actually that the AsyncAPI generator does not deliver what is promised on the AsyncAPI website. |
I would like to work on this issue. However, since this is modelina issue, should I create a new issue and then work on it or do something else? |
Describe the bug.
Hello, there awesome work on asyncapi spec!
So I copy and paste this example:
https://www.asyncapi.com/docs/tutorials/getting-started/hello-world
And run:
So it seems, like Modelina couldn't parse this file, and it could read names (thus, generating AnonymousSchema1)
Expected behavior
Well, generate the code
Screenshots
.
How to Reproduce
.
🥦 Browser
None
👀 Have you checked for similar open issues?
🏢 Have you read the Contributing Guidelines?
Are you willing to work on this issue ?
None
The text was updated successfully, but these errors were encountered: