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

Define how to handle unknown schema and message id's #34

Closed
jonaslagoni opened this issue Dec 14, 2021 · 4 comments
Closed

Define how to handle unknown schema and message id's #34

jonaslagoni opened this issue Dec 14, 2021 · 4 comments
Labels
enhancement New feature or request stale

Comments

@jonaslagoni
Copy link
Member

jonaslagoni commented Dec 14, 2021

Reason/Context

Sometimes it happens that users do not define id for schemas and names for messages.

In the JS parser, we currently assign ids such as anonymous-schema-x and names anonymous-message-x where x is just a counter that increases for each found anonymous schema or message. There is another suggestion to switch to a more usable algorithm for naming them - asyncapi/parser-js#176

Description

So how should be the algorithm that all parsers should implement?

@smoya
Copy link
Member

smoya commented Mar 8, 2022

Related somehow to this: asyncapi/parser-js#453 (comment)

@GreenRover
Copy link

Related somehow to this: asyncapi/parser-js#516

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

@github-actions github-actions bot added the stale label Aug 11, 2022
@smoya smoya removed the stale label Aug 11, 2022
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

@github-actions github-actions bot added the stale label Dec 10, 2022
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale
Projects
None yet
Development

No branches or pull requests

3 participants