v1.1.0 Features & Discussion

[rangav]

Hi All,

Thanks everyone for the support. Just want to give an update of whats coming for the next release. This will be major update since initial launch.

Here are the planned features for v1.1.0

New Features

• Custom Storage Location for collections to integrate with git, see README for details - Usability feedback #2 (status: completed)
• Nested folder support for Collections - Support Folders inside collection #8 (status: completed)
• Improved request creation workflow to save to collections faster - Need to create/run request before you can save it to collection? #7 (status: completed)
• Run Last Request from command palette. Usability feedback #2 (status: completed)
• Drap & Drop sorting for requests & folders (status: completed)
• Support Ctrl+S to save env vars Support Ctrl+S to save env vars #36 (status: completed)
• Create variable in env if doesn't exist when set - Create variable in env if doesn't exist when set #35 (status: completed )
• Postman import nested folder support (status: completed )
• Shift+Alt+F to format JSON body Shift+Alt+F to format JSON body #17
• proxy settings proxy settings? #61
• Show "Test Results" count in red if a test fails Show "Test Results" count in red if a test fails #55

BUG Fixes

• Fixes typed url text coverts to html symbol (status: completed) - typed url text coverts to html symbol #13
• Fixes state value missing in OAuth 2.0 Url (status: completed) - Support State for OAuth 2.0 #26
• Fixes enable scope for OAuth client credentials request (status: completed) - OAuth Authentication/Client Credentials should support scope #25
• Fixes Set Env Variable in Tests only works on last instance v1.0.7 - (status: completed) - Set Env Variable in Tests only works on last instance v1.0.7 #46
• Fixes Cannot test is equal to env variable - (status: completed) Cannot test is equal to env variable #58
• Fixes Can't Import Postman Collection for no reason Can't Import Postman Collection for no reason #77
• Fixes Broken format in JSON Body Broken format in JSON Body #63
• Fixes Import and save body parameters Import and save body parameters #47
• Can't save more than one environment variable from response Can't save more than one environment variable from response #81

ANNOUNCEMENT

• Thunder Client has crossed 50k downloads now, Thanks for the amazing response from everyone 🎉.

LIVE NOW

• Pulished v1.1.0 - documentation is updated partially.

If anything is not clear, please post your comments below, i will update documentation.

Please leave your feedback about v1.1.0 - features you like or features that need further improvements..

[Stancobridge]

Nice one

[anastely]

@rangav Can you add a Collection length under the collection name, like Postman?

collection name
24 requests

[rangav]

Hi @anastely can you please create a new feature request, I will add to product roadmap list.

[jongio]

ETA for next release with #26 included?

[rangav]

Hi @jongio I am planning to release by end of the day tomorrow.

[jongio]

Thanks. It would be cool if you could use the GitHub Releases feature so I can subscribe to releases.

[rangav]

Sure will start using Github release feature.

[rangav]

Hi All - version 1.1.0 is now published, please and let me know your feeback

[Pascal62223]

Hi,
Looking at Thunder-client and it looks great. Trying the 'test' feature and couldn't find a way to filter out the response based on a response property value when the response itself is an array of json objects.
Use case : How to filter filter response to only show location.latitude == "25" in below example. (trying json.location.latitude doesn't work obviously as it is an array)

[
{
"location" : {
"latitude" : "25",
"longitude" : "50"
}
},
{
"location" : {
"latitude" : "00",
"longitude" : "76"
}
}
]

[rangav]

Hi Pascal use json[0].location.latitude

[Pascal62223]

Thanks. I thought about that but was under impression it would only apply the test on he first object of the array and not to all objects in a loop.
I've tested, and it doesn't returns the proper object list. The attached picture show my real test case, and simplify to do the test at the root of the object.

I set the test to be json[0].timeZone equals 'Z', but teh response contains objects with timeZone equals to "+00:00" which doesn't satisfy the criteria.

[rangav]

Hi @Pascal62223 try json[0].timeZone == "+00:00", it does not have any time conversion functions built in. just try to match the strings

[Pascal62223]

Hi @rangav , Yes I do understand it does string match. The example is using timeZone as property, as I try to get all record with property timeZone equals to teh string 'Z'
To ensure there is no confusion (I have no intend to do time conversion), I use another example with the property 'uuid' which is a GUID string, and use the action 'contains'. Pure string match.
The response contains records with 'uuid' do not contains the string 'c93fbd6e' as specified in the test query criteria.
Also in that particular case the test result show an error (Cf. 2nd picture below) when doing the comparison apparently, and it is using only the first element of the array as I was suspecting (Cf. last picture result)

Error when executing comparison :

If use json[5].uuid, the test result error shows that only teh 5th element of teh array is being used.

[rangav]

Hi @Pascal62223 can you please create a separate bug for this, we can do discussion there. I will verify in the mean while.

[Pascal62223]

Ok. Thanks a lot