You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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.
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.
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
The text was updated successfully, but these errors were encountered: