- Use json drivers to support different json libraries like argonaut or
yoga-json
- Use continuations to simplify parsing and short-circuit bad requests
* cache `body` processing results (Buffer, String) with `Ref`
* add `readBodyAs(Buffer|Stream|String)` for accessing `body`
* fix tests
* add tests for `readBodyAsBuffer` and `readBodyAsString`
* move Body to HTTPure.Body and rename it to RequestBody
* add HTTPure.Body.toStream
* consolidate `readBodyAs(Buffer|String)` into `to(Buffer|String)`
and move `Ref` from top level `body` down to `buffer` and `string` fields
* fix tests
* import constructors explicitly
* revert changes
This reverts commit e53188c3e6d74ca00d3d891829ca91f0803b870b.
* update `Body.read` to return `RequestBody`
* First version of supporting non-string requests
* Clean up
* Minor cleanup
* Simplify to directly export the stream
* Add nl
* Clean up & add more testing
Co-authored-by: sigma-andex <sigma.andex@pm.me>
* v0.8.1
* Add failing tests for `Headers`
There's currently a bug with `Headers`:
if a header is created with uppercase characters, it can never be found.
The problem is that we only look for lowercase characters in the
`Lookup` instance for `Headers`.
* Convert `Headers` to use `CaseInsensitiveString`
In an effort to be more true to HTTP,
we make the header keys case-insensitive.
This fixes the issue of looking up a header where the casing is different,
Since `CaseInsensitiveString`s compare in a way that ignore casing.
The API for consumers for `Headers` stays the same,
but we get more correct code.
A win for all!
* v0.8.1
* Add the HTTP version to `Request`
The `node-http` `Request` has the HTTP version on it.
We can make it available in our `Request` for consumers.
We went the naive approach first and typed it as a string.
There is some structure to the version,
so we could attempt to parse it.
It's unclear what we would do if parsing failed though.
Maybe we want something like:
```PureScript
data Version
= Known { major :: Int, minor :: Int }
| Unknown String
```
That would allow us to parse the known format,
and fallback to accepting anything else.
It's definitely something to discuss anyway.
* Make HTTP version its own data type
There are only a handful of HTTP versions that are commonly used.
We can talk about those explicitly and fallback to any arbitrary version.
The changes here try to follow the patterns elsewhere in the code base.
Hopefully, it's not too far off.
