This message was deleted.
# generals
Slackbot
04/03/2023, 12:59 PMThis message was deleted.
t
Tom
04/03/2023, 1:02 PMNot right now - you need 3 stubs if you want 3 variations based on scenario state
a
Albert Vesker
04/03/2023, 1:05 PMSadge
Albert Vesker
04/03/2023, 1:05 PMThank u for fast answer!
t
Tom
04/03/2023, 1:05 PMNo probs
a
Albert Vesker
04/07/2023, 11:29 AMHi. I came with some ideas:
1. May be is it possible make common template? If so can u write some short guide?
2. May be some ideas to put variables
{{systemValue type='ENVIRONMENT' key='PATH'}}Albert Vesker
04/18/2023, 1:50 PM@Oleg Nenashev sry for ping, but may be u can suggest any ideas?
o
Oleg Nenashev
04/18/2023, 6:06 PMHi @Albert Vesker For the guide, it never hurts to have one indeed. I am currently working on making documentation more accessible for contributions, and all ideas about missing details/templates is always appreciated. For what it's worth, it is likely possible to create a WireMock extension which supports the syntax you want. FWIW I am a bit concerned about https://wiremock-community.slack.com/archives/C03NAEH5LVA/p1681289318528729 which might be a sign of a bug caused by this scenario state engine
Oleg Nenashev
04/18/2023, 6:07 PMMay be some ideas to put variablesI would advice against that. Better to write an extension IMHOto put it in RunTime to DockerContainer?{{systemValue type='ENVIRONMENT' key='PATH'}}
a
Albert Vesker
04/18/2023, 6:58 PM1. I agree that runTime variables are bad. It was Just as a variant
2. Thanks for extending docs, so I can just wait when u write it, right?) How much time do u expect u need for this example?) When to expect it?)
9 Views