Is your feature request related to a problem? Please describe.
Users cannot send JSON to an endpoint if the endpoint requires numbers to be JSON numbers. Currently Hoppscotch serializes all parameters as JSON strings.

Describe the solution you'd like
User input:

Expected

Some oauth2 server implementations use a different URL for generating an access_token and refreshing said access_token.
Arguably it's a questionable choice, since it's "only" a matter of grant_type being different, the return value being the same.

I would like to be able to specify the refresh token URL, with an optional field in the oauth2 configuration. If left empty, it should be the access

👋 THIS IS A GOOD FIRST ISSUE

🐞 Describe the bug

I noticed that the docs have some RST references to internal and external intersphinx objects. We should fix those and enable nitpicky = True by default.

P.S. It is okay to send small PRs to fix references gradually

💡 To Reproduce

Unco

建议使用ConcurrentHashMap
eg:private final Map<Class, ObjectParamMetadata> classToMetadata = new ConcurrentHashMap, ObjectParamMetadata>();

此处s是否可

Got has a very good coverage test-wise. Would be nice to port relevant tests that we're missing over to Ky.

Note: Not for https://github.com/sindresorhus/ky/blob/master/test/browser.js, but for everything else.

From time to time i see ppl using data instead of body which is wrong.
happened just recently in node-fetch/node-fetch#481 (comment)

how do you feel about adding a little warning message that can only appear once. (kinda like node reports that you are using experimental apis)

if ('data' in bodyInit && notWarned) {
  console.warn('use body i

Netty's event loop threads are spawned lazily, i.e. they are created on the first task is scheduled on. A user sometimes wants to ensure the event loop threads are started when the server starts up.