Is there a way to resolve results in the UI (for a...
# prefect-ui
a
Is there a way to resolve results in the UI (for a flow or task) to see the actual value, and not just where it was stored? Just for basic types like strings, ints, etc. Or even for dicts, even if it needs a resolver or something Edit: Also with task inputs, I’m not sure what’s happening, but they’re just showing up as
[]
. e.g.:
Copy code
{
  "param1": [],
  "param2": [],
}
1
j
Hey Andrew! We don’t show results in the ui, just their location. The simplest was to have them show in the ui is to treat them as an artifact
🙌 1
Task inputs show parameter keys and can also show task run relationships. We realize that can be a bit confusing - there’s a little explainer for that in the UI.
a
Interesting. Ok, good to know. So if I wanted to show input values, I’d also have to make artifacts for thos?
j
You mean task input values? (Ie not parameters?) Yeah I think creating artifacts would work? You could also print them ABs have them in the logs
a
Oh, sorry I just mean parameter values, rather than just the keys. Yeah looking through there, maybe it would make sense to make a table with inputs and outputs as an artifact
j
Cool that makes sense! (And just checking you’ve seen that flow run parameters have their own tab in the flow run page.)
a
Yes! That part is great. Has there ever been talk of doing something like that with task parameters? Also, with that in mind, do people ever run subflows instead of tasks to get that kind of functionality?
j
Oh that’s a great point about sub flow runs. I’ve not heard that but it would make sense. Showing task parameters isn’t something I’ve seen requested but if you want to open an issue in the Prefect repo, I can see it being something we’d consider.
Sorry I’m on mobile but I think this should be the right link: https://github.com/PrefectHQ/prefect/issues/new?template=3_feature_enhancement.yaml
a
Awesome Yeah I’ll think about that and consider adding an issue. Thanks for the response!
j
🙌