thunder-client-support
thunder-client-support copied to clipboard
Request response layout setting no longer respected since 1.18
Describe the bug Since update 1.18, the following setting is no longer respected:
"thunder-client.requestLayout": "Left/Right"
As you can see, my env is set to left/right, but my view is Top/Bottom. Before the update, this was working as intended. Changing the setting also does not change the layout of the request/response pages.

To Reproduce Set layout to left/right and open a request.
Expected behavior That the set layout is respected.
Platform:
- OS: Windows 10
- vscode version: 1.70.1
- extension version: 1.18
Solution: If only I knew
@kekonn did you change any setting in vscode?
that is the default Layout Left/Right, you dont need add any setting for that
No I did not change anything. And I know that is the default layout, and yet, the screenshot does not reflect the default layout. So why is that?
Change setting to top/bottom And see what happens?
after testing change it back to left/right
As described in my report, I tried this already. Changing the setting does not have a noticeable effect on the layout.
did you close the request view and re-open after changing setting?
I did a reload window between each setting change.
is your extension version v1.18.1?
share you share your settings screenshot for request layout?

thanks for sharing. strange something is not working.
Here are few things you can try
- Uninstall and re-install extension
- or downgrade extension to
v1.17.1
did you still have the issue?
Currently the issue is no longer present
Thanks @kekonn for confirmation 👍
Hi @rangav, I'm facing this issue right now, I re-installed Thunder Client, but still the response panel is at the bottom, even changing the configuration to be in the Right position.
Hi @manuelvalenzuela can you share screenshot of setting and request view?
and also version of extension used?
Hi @rangav, I'm sorry for not answering before. I can't live without Thunder Client :D, so I reinstalled vscode, and everything is working good now! I don't have the screenshot, but was using the latest version of the extension.