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

Display service URI on deployment pages instead of its id when name is not available #680

Open
3 tasks
stalniy opened this issue Jan 21, 2025 · 4 comments
Open
3 tasks

Comments

@stalniy
Copy link
Contributor

stalniy commented Jan 21, 2025

WHY

It's hard to understand the purpose of deployment without seeing its name. As names are not shared between browsers, users need to specify the same name across different browsers or remember deployment ids.

We can improve UX a bit by showing service host URI if name is not specified

What

Display service URI on deployment pages instead of its id when name is not available

Acceptance

  • display service URI on deployment pages instead of its id when name is not available
  • when name is available, it should be used instead
  • when both name and URI is not available, display deployment id
@stalniy
Copy link
Contributor Author

stalniy commented Jan 21, 2025

One service may have multiple URI(s). Which one should be displayed on deployment page?
My assumption is the one which doesn't contain provider host in it.

@anilmurty @baktun14 could you please validate my assumption?

@ygrishajev
Copy link
Contributor

I think this would only work when there's a yaml with a single defined accept. It would help a lot already. Otherwise we could show the first one and show a list of the rest in a tooltip on hover.

@baktun14
Copy link
Contributor

Yea like @ygrishajev said it's based on the accept property in the SDL, so yes there can be multiple. I agree with showing the first one and other in tooltip.

@anilmurty
Copy link

agreed with what was already said (first + tooltip)

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

4 participants