In = syntax,

• double quotes (")
• back slashes (\)
• non-ascii characters

are escaped in json.dumps:

$ http -v httpbin.org/post                                      \
    dquote='\"'                                                 \
    multi-line='line 1\nline 2'                               

https://code.nasa.gov/

Maybe related to how the page causes a PROTOCOL_TIMEOUT?

From https://bugs.chromium.org/p/chromium/issues/detail?id=951684

Currently, if look at the windows_e2e tests on circle under the write e2e files step, you will see this warning:

Error autodetecting timing type, falling back to weighting by name. Autodetect no matching filename or classname.  If file names are used, double check paths for absolute vs relative.
Example input file: "e2e\\api\\add-many.e2e.1.ts"
Example file from timings: "C:\\Users\\****

Expected behavior

Before Skaffold supported parallel local builds, we used profiles for that matter, building profiles concurrently.
That allows us to stream build log for each profile (one profile per image) to file named like {LOGS_DIR}/build/{PROFILE_NAME}.log.

I couldn't load and build the project using the latest qt creator and the wiki guide for building, i think it's out dated, please update and add more details for beginners who want to contribute.

Correct the terminology used in code and documentation so that it is consistent with HTTPie and web standards. Examples:

• body parameter -> data field
• operator -> separator

I think the work you've done on this is amazing. Seems like a great project, but your README is a bit bloated and hard to decipher. Might I suggest you condense it down into a set of readable chunks and maybe link off to the wiki for the more detailed bits.

Its only my opinion, but I find that answering the following questions, in order, helps to simplify docs.

• who? - who wrote the p

Affected Projects
React

Is your feature request related to a problem? Please describe.
Was looking through the change log and the new documentation but could not find any reference to the deprecated DataController.

Describe the solution you'd like
Would be great to get some documentation on the recommended way to migrate from using DataController to not using it.

**Descr