Commit Graph

7 Commits

Author SHA1 Message Date
Thomas Honeyman
6ce52417f7
Migrate from purty to purs-tidy (#178)
* Replace purty with purs-tidy

* run purs-tidy
2021-11-06 12:37:31 -07:00
Connor Prussin
1ad5a08306
Add code formatting with purty (#171)
* Add code formatting with purty

* Purtify code
2021-03-22 12:02:36 -07:00
Tim McIver
b3eb977096
Fix HTTPure.Utils.replacePlus (#166)
* Create failing test.

* Fix code so failing test passes.
2020-11-14 13:09:07 -08:00
Gareth Smith
4d5518eff5 Update the tests to work with purescript-spec v4.0.0 (#147)
This version was already being pulled in by the package set, so the
tests were breaking.

Also update bower.json to match the package set dependencies.
2019-09-23 13:14:21 -07:00
Hardy Jones
c208dffb7b Add HTTP version (#137)
* 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.
2019-04-25 10:13:04 -07:00
Connor Prussin
1bde8b4b1d
Consolidate APIs (#104)
* Consolidate APIs

* Use partial function approach instead of Streamable typeclass

* Clean up
2018-08-26 21:54:04 -07:00
Connor Prussin
0fa3d1a90c Clean up tests and examples (#86) 2017-10-26 17:19:30 -04:00