Describe the bug
Changing the HTTP method to POST just after creating new request in Request form doesn't set it to correct value.
To Reproduce
Steps to reproduce the behavior:
Go to Fetch Client extension by clicking the left icon in VSCode
Click on Collection tab
Click on '...' button to the right of the collection name in left panel. Then select in the menu 'New Request'
Enter the name of new request in the top line input. Then type Enter
The new Request is created in the left panel with the HTTP GET method.
In the right panel, change HTTP method dropdown to POST
Type CTRL+S to save the change.
The method in left panel is still 'GET'
Fill the information in the right panel to create de HTTP request
Suppose that you use a backend framework for your API, set the allowed method to POST (e.g. routes files for PHP Laravel Framework)
Send the request with Fetch-client
The response returned an HTTP "405 Error - Method not allowed" showing that GET method was used to send the request
That is the bug
Expected behavior
Do not returns an HTTP 405 Error when backend route allows only HTTP POST method.
Screenshots
Desktop (please complete the following information):
OS: Windows 10, build 19045.3324 (22H2)
Fetch Client Version 1.3.0
VS Code Version 1.81.1
Additional context
I show that there are many tabs opened in Fetch-Client extension view with the same HTTP request. Maybe that is the bug
I have been installed the Thunder Client extension and it enabled. Hope that there is no conflict with Fetch-content extension
Describe the bug Changing the HTTP method to POST just after creating new request in Request form doesn't set it to correct value.
To Reproduce Steps to reproduce the behavior:
Expected behavior Do not returns an HTTP 405 Error when backend route allows only HTTP POST method.
Screenshots
Desktop (please complete the following information):
Additional context I show that there are many tabs opened in Fetch-Client extension view with the same HTTP request. Maybe that is the bug I have been installed the Thunder Client extension and it enabled. Hope that there is no conflict with Fetch-content extension