Tihomir Surdilovic

> feature that allows users to throw an error based on runtime conditions somewhere in their flow trying to understand ^^, its not somewhere its part of (from example) action...

to add, what im thinking is more like: actions: - name: is-room-available functionRef: refName: check-if-room-is-available arguments: id: 123 actionDataFilter: toStateData: .roomAvailable

you could then also make these if/else checks with throw reusable components across multiple actions maybe

> Not sure I understand what you mean by that make these conditions reusable like we do for errors so throw-if-not-true condition: ${ .roomAvailable == false } errorRef: refName: room-not-available...

or something like: actions: - name: is-room-available functionRef: refName: check-if-room-is-available arguments: id: 123 actionDataFilter: toStateData: .roomAvailable outputConditions: - type (maybe???) default to throw? condition: "..." errorRef: "..."

Got it, ok will keep reading. One think that comes to mind in your example is what if you don't control the check if room available action (its impl), how...

In your example where is the refName: foo.greet function definition? is the function def named "greet" and you append the namespace to it?

Thanks, yeah i put a comment on that associated issue..do really like it but then why not {namespace}.{stateName} {namespace}.{actionName} {namespace}.{eventDefName} ... I think these type of changes are awesome but...

Yeah I understand, i think with this also comes a lot of possible issues on user level (possible typos since you have to define a namespace in each action, maybe...

One more question, does this apply only for "rest" action type? For everything else the resource / uri would be defined inside the offloaded json/yaml (openapi/asyncapi/grpc, etc)