Shared variables are no longer accessible when selecting "No Environment" after update

[atrakaz]

• VSCode Version: 1.38.1
• OS Version: Windows 10 Pro
• REST Client Version: 0.22.1
  Note: Worked yesterday before the new version

Steps to Reproduce:

1. ...>AppData>Roaming>Code>User>settings.json:
   "rest-client.environmentVariables": {
   "emptyEnvironment": {
   },
   "$shared": {
   "testUrl": "http://www.google.com/"
   },
   }

2. Select REST Client Environment: "No Environment"

3. test.http:

GET {{testUrl}}

=> Error message: "Cannot convert undefined or null to object"

When selecting "emptyEnvironment", Shared variables are accessible.

Conclusion:
This breaks the following statement when selecting the following: "No environment (You Can Still Use Variables Defined In $shared Environment)"

[Huachao]

@atrakaz nice catch, I have fixed the issue and will be published in next release 😄

[jezikk]

@Huachao When this bugfix will be published to the production please? I started VSCode today and the error message is still shown. Shared environments are not available in my project.

[Huachao]

@jezikk version 0.22.1 is not totally ready, I am still working on some other features, and after that the 0.22.1 will be published

[jezikk]

It's weird, but I already have version 0.22.1 installed.

[Huachao]

@jezikk sorry the upcoming release version should be 0.22.2

[Huachao]

@jezikk @atrakaz you can try the latest version 0.22.2 to verify it.

[jezikk]

It's oka now. Thanks!

[atrakaz]

It works. Thanks!

[cedx]

This issue is still here with VSCode 1.45.0 (Windows 10 x64) and REST Client 0.23.2.

[Huachao]

@cedx I can't repro your case, could you please double-check the defined shared environment variables in your settings and the referenced variable name in your .http file?