Open jsonporter opened 1 year ago
@tsheiner - do you have any thoughts concerns with removing the link back to 'console' in the dropdown? Thinking we could either just rely on the logo (which directs to the same value as the link console
) or maybe we just add logic to ensure that its included in the list but if the user adds it manually we respect the index/location for where it appears?
I'm not clear what 'console' link does?
If I select to follow any of these custom links I go to whatever url is specified without our console header, right?
I don't understand the case where I am not in Console but can still access the dropdown with Console link???
Thanks for reporting this, Jason! This captures our use-case and would be very useful features to have.
Hello 👋, this issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will engage on it to decide if it is still applicable. Thank you for your contribution and understanding! 🙏
Motivation: Why do you think this is important?
Users have requested two changes to how the navigation handles
FLYTE_NAVIGATION.items[]
. Currently, when a user exportsFLYTE_NAVIGATION
and provides values for custom navigation usingitems[]
we render a dropdown with those links.Example from documentation:
items[{title:"foo", url:"bar", target:"_blank"}]
)BASE_URL
as a default in the dropdown or at least gives users the choice where it appears in the list. This could work a couple of ways (eg, we could just rely on users clicking the logo to return toconsole
from some external app or we could even add some sort of logic when creating that list to ensure thatconsole
is present but users could choose which position in the listconsole
appears.Goal: What should the final outcome look like, ideally?
console
appears in that list or if it appears at all.Propose: Link/Inline OR Additional context
No response
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?