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

how about use x-name or something for generated name? #107

Open
scink opened this issue Mar 17, 2020 · 5 comments
Open

how about use x-name or something for generated name? #107

scink opened this issue Mar 17, 2020 · 5 comments

Comments

@scink
Copy link
Contributor

scink commented Mar 17, 2020

Screenshot 2020-03-17 at 19 30 25

how about use x-name or something for generated name?
@raveclassic
Copy link
Contributor

When I was working on AsyncAPI support I didn't find anything else except full path because of some reasons (don't remember). Perhaps because of name clashes.

@scink
Copy link
Contributor Author

scink commented Mar 17, 2020

is there any way to set the name? i mean, does async api has something that can be used?

@scink
Copy link
Contributor Author

scink commented Mar 17, 2020

looks like, only using Specification Extensions, like x-name or something

@scink scink changed the title can tags be used to create readable channel names? how about use x-name or something for generated name? Mar 18, 2020
@scink
Copy link
Contributor Author

scink commented Jun 23, 2020

any new thoughts about this?

@raveclassic
Copy link
Contributor

There's no support for spec extensions at the moment, and I suppose there will never be in the core. It's too specific.
OTOH we could think about comprehensive plugin system which would allow any kind of extra feature without complicating the core.

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

No branches or pull requests

2 participants