Closed twilkinson closed 7 months ago
Can you please send me response sample for 2
REQUEST:
RESPONSE:
ENVIRONMENT:
variable timezone_q is not set
Why do you want to do “timezone” when timezone works. Is the a reason behind that.
It's just a test. I'm thinking of a case where the response Json has names with special characters in them, for example:
{ "first:last": "Joe Smith", "first.last": "Joe Smith" }
@twilkinson I have fixed it now pls try like this below
That's a lot better! I see you're now correctly setting values where the response property is 0 - great!
The only thing remaining is that it doesn't seem to save the value where the response property is either of
For example it doesn't seem to save the following value, OR
from the RESPONSE
Otherwise, it's looking great!
@twilkinson i don't think we should save null or empty string parameters.
What's your reason for that? They are values after all :-)
Ok 🙂 @twilkinson i will include them. Please give me a review when you get a chance.
Thanks for the quick responses.
I have come across a real-world example that I think can only be handled if you support quoted parameter values when setting variables.
I need to reference the url object marked with the magenta arrow in this response:
I think it has to be referenced using quotes, like this.
assets."https!!!devtest!driftscape!com!newsatlas!branding!drift!favicon.png".url
The current syntax (below, without the quotes) won't work because of the .png
in the object name.
assets.https!!!devtest!driftscape!com!newsatlas!branding!drift!favicon.png.url
You've done a great job with this VS Extension and I think with these changes it can become a workable alternative to Postman. Then I'll be happy give a good review.
Please try now with version 1.1.74
Please have a look at these tests: TEST
RESPONSE
TEST RESULTS
I think the two that Failed should have Passed?
Please have a look at these tests: TEST
RESPONSE
TEST RESULTS
I think the two that Failed should have Passed?
@twilkinson Please try now
Please try now with version 1.1.74
@twilkinson Did you try this fix ?
@subasraj That fixed things - thanks again for your quick response.
@twilkinson Thanks for the review :)
I like your plugin but it would be more useful if the "value" for "Json Response" was more complete.
For example:
Thanks,