#6410 [Core feature] Support `typing.Literal` as flyte type in tasks Issue created by HansBambel Motivation: Why do you think this is important? I am using in our pipelines quite a few

Literal

definitions in our functions. When putting a

@task

decorator from Flyte onto these functions, it also works, but in the UI it shows up as

feature: "single (PythonPickle) blob"

in the "input"-tab. When changing this to

str

it shows up as a simple string:

feature:"outcome"

. Goal: What should the final outcome look like, ideally? It would be nice to have the

typing.Literal

parameter also render as string in the UI. Describe alternatives you've considered Instead of using the more strict

typing.Literal

we could use a normal

str

type, but this removes stricter typing. 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