replace query string with entire object from custom values

[noahdietz]

This is an issue pulled from the original repo.

Instead of iterating over query string values supplied in the custom values, it would be better to just inject the entire object as given, to avoid include params that were omitted in the custom values definition.

[RajeshAjjarapu]

I am just trying to understand how do I provide query string value through custom value option. Any help is appreciated

[noahdietz]

@RajeshAjjarapu have you seen the custom values used for testing? test/process/documents/customValuesTest.json

Try copying this and stripping out what you don't need. Then specify its consumption using the --customValuesFile CLI flag or customValuesFile option field.

[RajeshAjjarapu]

Thanks Noah for responding. I am just trying to understand how do we generate this file or prepare custom values file. For example, I am trying to over ride the value in query string with value of my choice so that test case gets updated.
'qs': {"compartmentId":"elit labore","name":"elit reprehenderit minim laboris" ....

[RajeshAjjarapu]

oopsie, my bad. Figured and it got updated. If further questions, I will reach out thanks a lot

[RajeshAjjarapu]

Hi Noah,

Any suggestions if we don't need to pass a query parameter itself ?

[noahdietz]

I'm not sure I understand. You want to exclude a query param? If yes, then that's what this issue is about, excluding query params that aren't explicitly defined in the customValues. It would allow you to supply an empty object for the query params and none would be included in the generated output.

[RajeshAjjarapu]

You got it right. ok. let's say I have 5 query params per spec. I want only two to be included in the request. I tried passing null values, but that query param is not being ignored. We don't want to pass query params with null values.

[noahdietz]

Ok. That's what I was saying, this issue is about supporting explicit exclusion of query params. It is not support right now.