Describe the bug
When I pull the resize button of the code editor, it doesn't the resize the code in the editor.

To Reproduce
Steps to reproduce the behavior:

1. Click the resize button on the code editor and drag it down
2. The code doesn't resize

Expected behavior
I expected the code to resize as I drag down the button.

Screenshots
If applicable, add screenshots to

Describe the bug
"Import from URL" for query params does not update the UI

To Reproduce

1. paste http://localhost:4000/path?param=test in the url
2. go to query tab
3. click "import from url"
4. Note that the tab shows the count of query params (1) but the keyvalue table does not update
5. Activate a different request in the sidebar
6. Go back to the previous request
7. Note t

🐞 Describe the bug

TraceConfig.on_response_chunk_received doesn't trace if the response body is read from ClientResponse.content

This behavior isn't obvious when looking at Tracing Reference, [Streaming Response Content](https://docs.aiohttp.org/e

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

此处s是否可

I've read many similar closed issues, but haven't found a good documented solution on what can I do as a consumer of ky package if I need to support e.g iOS 10.0 browser (that breaks on async/await support currently).

I agree that it's not related to ky itself, but can be a nice help for the consumers of the package.

In our particular can we don't use babel (we use typescript), so I'm

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

In our codebase, we push RequestContext and immediately run some code with try-with-resources.
For example:

try (SafeCloseable ignored = ctx.push()) {
    logger.trace(decorate(msg));
}

If RequestContext provides run(Runnable) or call(Callable) we can reduce boilerplate code and simplify it.

ctx.run(() -> logger.trace(decorate(msg));

This is inspired by g