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
Browsing relative names has UX issues. We show root as or which is useless. Ideally that should show the endpoint of what resolves the name, Issues is there can be multiple roots, so there is no "single" root to show.
For now, Extension only accepts a single root, so theoretically for now it is only one root.
Maybe we concatenate the roots and show that instead of
The text was updated successfully, but these errors were encountered:
Browsing relative names has UX issues. We show root as or which is useless. Ideally that should show the endpoint of what resolves the name, Issues is there can be multiple roots, so there is no "single" root to show.
For now, Extension only accepts a single root, so theoretically for now it is only one root.
Maybe we concatenate the roots and show that instead of
The text was updated successfully, but these errors were encountered: