Do we need automated tests for this trivial change?
I didn't find any existing desktop tests for specific HTTP methods. Just some basic ones like should be able to select a method by clicking and should be able to select a method by navigating with keyboard.

Do we need automated tests for this trivial change? I didn't find any existing desktop tests for specific HTTP methods. Just some basic ones like should be able to select a method by clicking and should be able to select a method by navigating with keyboard.

I think it's ok. There is not much to test as these words are passed "as-is" to Node.js

Thank you for the contribution and for updating the contributing guidelines.

Can you fix the linting/formatting? I will then merge and it will be included in the next release.

Strange, the command npm run lint didn't gave any hints about the issues:

Also the command npm run format didn't seem to work properly on my machine:

But I manually executed prettier on the changed files and hope the CI linter will accept it now.

Can you re-trigger the CI pipeline?

I've triggered the ci pipeline in my fork and fixed all the upcoming issues.
=> This PR should be merge ready - finally! :-)

Strange, the command npm run lint didn't gave any hints about the issues:

Also the command npm run format didn't seem to work properly on my machine:

But I manually executed prettier on the changed files and hope the CI linter will accept it now.

Can you re-trigger the CI pipeline?

Yeah sorry the formatting was failing not the linting. But the error you get is really strange, the command usually works (I use it in multiple env, Windows, Linux , etc.). I have no idea what happened.

Thanks for fixing everything 🙂