You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that, when using the grpc engine, variables are used literally. In this case I would expect {{ email }} to be replaced with [email protected] however my server receives the string of {{ email }}. Is this expected when using the grpc engine? It would be really useful to be able to use variables, especially when combined with tools like faker to create randomish test data.
(Apologies if there are any yaml formatting inconsistencies, GitHub didn't handle pasting too well)
I've got the same problem, looks like this can be fixed by changing const args = ops[rpcName] -> const args = this.helpers.template(ops[rpcName], context)
in the step function @kenju
It appears that, when using the grpc engine, variables are used literally. In this case I would expect
{{ email }}
to be replaced with[email protected]
however my server receives the string of{{ email }}
. Is this expected when using the grpc engine? It would be really useful to be able to use variables, especially when combined with tools like faker to create randomish test data.(Apologies if there are any yaml formatting inconsistencies, GitHub didn't handle pasting too well)
The text was updated successfully, but these errors were encountered: