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

Documentation about service name #187

Open
karmingc opened this issue May 15, 2023 · 1 comment
Open

Documentation about service name #187

karmingc opened this issue May 15, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@karmingc
Copy link

karmingc commented May 15, 2023

Hi,

Is there any documentation what service name is supported? For example, when publishing a new graphql schema with a service such as test/test, it will be published correctly as it will be listed in the /schema/latest API. However, when navigating with the UI, it will lead to a page with Select a service from the list, for example, navigating to <registry_url>/#/schema/test/test. So it seems to be an issue with the client's path resolution. Maybe add a validation to avoid service names with a slash?

Likewise, what would be the appropriate process in deleting the said example as it's returning a 404?
For example, DELETE /schema/test/test.

Thanks.

@tot-ra tot-ra added the bug Something isn't working label May 25, 2023
@tot-ra
Copy link
Owner

tot-ra commented May 25, 2023

good point, validation would be nice. PR is welcome )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants