Function arguments vs action data filter #558
Replies: 3 comments 1 reply
-
Imo yes, besides filtering data that action params can access, action data filter also provides the useResults and toStateData
If action filter fromStateData is specified, then its results define the json that can be used in properties. If not specified, yes action props can use the whole state data |
Beta Was this translation helpful? Give feedback.
-
I agree to all settings around action data filter, what I am still not clear about is the arguments of the function that are set on Is it only needed for graphql or all? What got me thinking is that arguments in the above link are again expressions so it seems to be yet another filter expression. My main question is action data vs arguments - what’s the difference and why we need both? |
Beta Was this translation helpful? Give feedback.
-
@mswiderski I'm closing this one since it's outdated due to the new version we have now if you don't mind taking a look: https://github.com/serverlessworkflow/specification/blob/main/dsl.md |
Beta Was this translation helpful? Give feedback.
-
Hi,
i am looking into functions within action state and started to think what kind of relationship there is between function’s arguments and action data filters?
Arguments are not really described in the spec in that manner so not sure how others interpret it, more specificly:
I started to think that arguments might be unneeded level of data and functions could simply get action data based on the filter.
What do you guys think? Or how other runtimes approach this part of the spec?
Beta Was this translation helpful? Give feedback.
All reactions