Skip to content
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

Support dynamic asyncapi specs as sql changes #169

Open
wants to merge 70 commits into
base: develop
Choose a base branch
from

Conversation

akrambek
Copy link
Contributor

Description

Support dynamic asyncapi specs as sql changes.

Fixes #126

@akrambek akrambek marked this pull request as ready for review January 23, 2025 21:09
Comment on lines 62 to 64



Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Formatting

import org.springframework.context.annotation.Configuration;

@Configuration
@ConfigurationProperties(prefix = "app.gen")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this intended to be api.gen?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess you are saying whether we need a prefix at all?

petstore_customers-stream-identity:
address: "/petstore_customers-stream-identity"
messages:
PETSTORE_CUSTOMERSMessage:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
PETSTORE_CUSTOMERSMessage:
PetstoreCustomersMessage:

Let's make the spec more readable, by converting PETSTORE_CUSTOMERS to PetstoreCustomers for example.

protocol: http
channels:
petstore_customers-stream-identity:
address: "/petstore_customers-stream-identity"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to review the generated API paths for HTTP spec to make sure they are as natural as possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants