#3773 [UI Feature] Update FLYTE_NAVIGATION behavior Issue created by jsonporter 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 exports

FLYTE_NAVIGATION

and provides values for custom navigation using

items[]

we render a dropdown with those links. Example from documentation:

{
    color:"white",          // optional - default NavBar text color, if not provided uses Flyte colors
    background:"black",     // optional - default NavBar background color, if not provided uses Flyte colors
    console:"FlyteConsole"  // optional - name of the default navigation, if not provided uses "Console"
    items:[                 // required - if no dropdown needed provide an empty array
        {title:"Remote", url:"<https://remote.site/>"},
        {title:"Dashboard", url:"+/projects/flytesnacks/executions?domain=development&duration=all"},
        {title:"Information", url:"/information"}
    ]
}

1. Add the ability to have dropdown links open in a new tab (current behavior redirects/adds to history) via some optional property (eg,

items[{title:"foo", url:"bar", target:"_blank"}]

) 2. Do not include

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 to

console

from some external app or we could even add some sort of logic when creating that list to ensure that

console

is present but users could choose which position in the list

console

appears. Goal: What should the final outcome look like, ideally? 1. Users can choose to have certain links in the dropdown open in new tabs. 2. Users can choose where

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? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte