thunderstrike/purescript-httpurple
thunderstrike/purescript-httpurple
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
c208dffb7b
purescript-httpurple/test/Test/HTTPure/QuerySpec.purs

66 lines
2.5 KiB
Haskell
Raw Normal View History

Clean up tests and examples (#86)
2017-10-26 21:19:30 +00:00
module Test.HTTPure.QuerySpec where
Improve and simplify APIs (#68)
2017-09-26 06:08:07 +00:00
import Prelude
Add tooling for working with query parameters (#69)
2017-09-26 07:14:06 +00:00
import Data.Tuple as Tuple
PureScript 0.12 support (#89) - Upgrade all dependencies - Use Effect instead of Eff - Use Foreign.Object instead of StrMap - Use Effect.Ref instead of Control.Monad.ST - Drop SecureServerM, it's the same as ServerM now
2018-07-08 23:16:48 +00:00
import Foreign.Object as Object
Improve and simplify APIs (#68)
2017-09-26 06:08:07 +00:00
import Test.Spec as Spec
import HTTPure.Query as Query
Clean up tests and examples (#86)
2017-10-26 21:19:30 +00:00
import Test.HTTPure.TestHelpers as TestHelpers
import Test.HTTPure.TestHelpers ((?=))
Improve and simplify APIs (#68)
2017-09-26 06:08:07 +00:00
Clean up tests and examples (#86)
2017-10-26 21:19:30 +00:00
readSpec :: TestHelpers.Test
Improve and simplify APIs (#68)
2017-09-26 06:08:07 +00:00
readSpec = Spec.describe "read" do
Add tooling for working with query parameters (#69)
2017-09-26 07:14:06 +00:00
Spec.describe "with no query string" do
PureScript 0.12 support (#89) - Upgrade all dependencies - Use Effect instead of Eff - Use Foreign.Object instead of StrMap - Use Effect.Ref instead of Control.Monad.ST - Drop SecureServerM, it's the same as ServerM now
2018-07-08 23:16:48 +00:00
Spec.it "is an empty Map" do
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 17:13:04 +00:00
req <- TestHelpers.mockRequest "" "" "/test" "" []
PureScript 0.12 support (#89) - Upgrade all dependencies - Use Effect instead of Eff - Use Foreign.Object instead of StrMap - Use Effect.Ref instead of Control.Monad.ST - Drop SecureServerM, it's the same as ServerM now
2018-07-08 23:16:48 +00:00
Query.read req ?= Object.empty
Add tooling for working with query parameters (#69)
2017-09-26 07:14:06 +00:00
Spec.describe "with an empty query string" do
PureScript 0.12 support (#89) - Upgrade all dependencies - Use Effect instead of Eff - Use Foreign.Object instead of StrMap - Use Effect.Ref instead of Control.Monad.ST - Drop SecureServerM, it's the same as ServerM now
2018-07-08 23:16:48 +00:00
Spec.it "is an empty Map" do
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 17:13:04 +00:00
req <- TestHelpers.mockRequest "" "" "/test?" "" []
PureScript 0.12 support (#89) - Upgrade all dependencies - Use Effect instead of Eff - Use Foreign.Object instead of StrMap - Use Effect.Ref instead of Control.Monad.ST - Drop SecureServerM, it's the same as ServerM now
2018-07-08 23:16:48 +00:00
Query.read req ?= Object.empty
Add tooling for working with query parameters (#69)
2017-09-26 07:14:06 +00:00
Spec.describe "with a query parameter in the query string" do
PureScript 0.12 support (#89) - Upgrade all dependencies - Use Effect instead of Eff - Use Foreign.Object instead of StrMap - Use Effect.Ref instead of Control.Monad.ST - Drop SecureServerM, it's the same as ServerM now
2018-07-08 23:16:48 +00:00
Spec.it "is a correct Map" do
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 17:13:04 +00:00
req <- TestHelpers.mockRequest "" "" "/test?a=b" "" []
PureScript 0.12 support (#89) - Upgrade all dependencies - Use Effect instead of Eff - Use Foreign.Object instead of StrMap - Use Effect.Ref instead of Control.Monad.ST - Drop SecureServerM, it's the same as ServerM now
2018-07-08 23:16:48 +00:00
Query.read req ?= Object.singleton "a" "b"
Add tooling for working with query parameters (#69)
2017-09-26 07:14:06 +00:00
Spec.describe "with empty fields in the query string" do
Spec.it "ignores the empty fields" do
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 17:13:04 +00:00
req <- TestHelpers.mockRequest "" "" "/test?&&a=b&&" "" []
PureScript 0.12 support (#89) - Upgrade all dependencies - Use Effect instead of Eff - Use Foreign.Object instead of StrMap - Use Effect.Ref instead of Control.Monad.ST - Drop SecureServerM, it's the same as ServerM now
2018-07-08 23:16:48 +00:00
Query.read req ?= Object.singleton "a" "b"
Add tooling for working with query parameters (#69)
2017-09-26 07:14:06 +00:00
Spec.describe "with duplicated params" do
Spec.it "takes the last param value" do
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 17:13:04 +00:00
req <- TestHelpers.mockRequest "" "" "/test?a=b&a=c" "" []
PureScript 0.12 support (#89) - Upgrade all dependencies - Use Effect instead of Eff - Use Foreign.Object instead of StrMap - Use Effect.Ref instead of Control.Monad.ST - Drop SecureServerM, it's the same as ServerM now
2018-07-08 23:16:48 +00:00
Query.read req ?= Object.singleton "a" "c"
Add tooling for working with query parameters (#69)
2017-09-26 07:14:06 +00:00
Spec.describe "with empty params" do
Query param fixes (#128) * Represent emtpy query parameters as empty strings instead of "true" * Encode and decode query params Fixes #126 * Pass invalid query parameters through instead of ignoring them * Decode the plus sign `+` as a space ` ` in query string * Decode percent encoding in path segments * Update History.md
2018-11-06 17:45:37 +00:00
Spec.it "uses '' as the value" do
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 17:13:04 +00:00
req <- TestHelpers.mockRequest "" "" "/test?a" "" []
Query param fixes (#128) * Represent emtpy query parameters as empty strings instead of "true" * Encode and decode query params Fixes #126 * Pass invalid query parameters through instead of ignoring them * Decode the plus sign `+` as a space ` ` in query string * Decode percent encoding in path segments * Update History.md
2018-11-06 17:45:37 +00:00
Query.read req ?= Object.singleton "a" ""
Add tooling for working with query parameters (#69)
2017-09-26 07:14:06 +00:00
Spec.describe "with complex params" do
PureScript 0.12 support (#89) - Upgrade all dependencies - Use Effect instead of Eff - Use Foreign.Object instead of StrMap - Use Effect.Ref instead of Control.Monad.ST - Drop SecureServerM, it's the same as ServerM now
2018-07-08 23:16:48 +00:00
Spec.it "is the correct Map" do
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 17:13:04 +00:00
req <- TestHelpers.mockRequest "" "" "/test?&&a&b=c&b=d&&&e=f&g=&" "" []
Add Headers.empty and Headers.header (#78)
2017-09-29 14:25:31 +00:00
Query.read req ?= expectedComplexResult
Query param fixes (#128) * Represent emtpy query parameters as empty strings instead of "true" * Encode and decode query params Fixes #126 * Pass invalid query parameters through instead of ignoring them * Decode the plus sign `+` as a space ` ` in query string * Decode percent encoding in path segments * Update History.md
2018-11-06 17:45:37 +00:00
Spec.describe "with urlencoded params" do
Spec.it "decodes valid keys and values" do
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 17:13:04 +00:00
req <- TestHelpers.mockRequest "" "" "/test?foo%20bar=%3Fx%3Dtest" "" []
Query param fixes (#128) * Represent emtpy query parameters as empty strings instead of "true" * Encode and decode query params Fixes #126 * Pass invalid query parameters through instead of ignoring them * Decode the plus sign `+` as a space ` ` in query string * Decode percent encoding in path segments * Update History.md
2018-11-06 17:45:37 +00:00
Query.read req ?= Object.singleton "foo bar" "?x=test"
Spec.it "passes invalid keys and values through" do
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 17:13:04 +00:00
req <- TestHelpers.mockRequest "" "" "/test?%%=%C3" "" []
Query param fixes (#128) * Represent emtpy query parameters as empty strings instead of "true" * Encode and decode query params Fixes #126 * Pass invalid query parameters through instead of ignoring them * Decode the plus sign `+` as a space ` ` in query string * Decode percent encoding in path segments * Update History.md
2018-11-06 17:45:37 +00:00
Query.read req ?= Object.singleton "%%" "%C3"
Spec.it "converts + to a space" do
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 17:13:04 +00:00
req <- TestHelpers.mockRequest "" "" "/test?foo=bar+baz" "" []
Query param fixes (#128) * Represent emtpy query parameters as empty strings instead of "true" * Encode and decode query params Fixes #126 * Pass invalid query parameters through instead of ignoring them * Decode the plus sign `+` as a space ` ` in query string * Decode percent encoding in path segments * Update History.md
2018-11-06 17:45:37 +00:00
Query.read req ?= Object.singleton "foo" "bar baz"
Add tooling for working with query parameters (#69)
2017-09-26 07:14:06 +00:00
where
expectedComplexResult =
PureScript 0.12 support (#89) - Upgrade all dependencies - Use Effect instead of Eff - Use Foreign.Object instead of StrMap - Use Effect.Ref instead of Control.Monad.ST - Drop SecureServerM, it's the same as ServerM now
2018-07-08 23:16:48 +00:00
Object.fromFoldable
Query param fixes (#128) * Represent emtpy query parameters as empty strings instead of "true" * Encode and decode query params Fixes #126 * Pass invalid query parameters through instead of ignoring them * Decode the plus sign `+` as a space ` ` in query string * Decode percent encoding in path segments * Update History.md
2018-11-06 17:45:37 +00:00
[ Tuple.Tuple "a" ""
Add tooling for working with query parameters (#69)
2017-09-26 07:14:06 +00:00
, Tuple.Tuple "b" "d"
, Tuple.Tuple "e" "f"
Query param fixes (#128) * Represent emtpy query parameters as empty strings instead of "true" * Encode and decode query params Fixes #126 * Pass invalid query parameters through instead of ignoring them * Decode the plus sign `+` as a space ` ` in query string * Decode percent encoding in path segments * Update History.md
2018-11-06 17:45:37 +00:00
, Tuple.Tuple "g" ""
Add tooling for working with query parameters (#69)
2017-09-26 07:14:06 +00:00
]
Improve and simplify APIs (#68)
2017-09-26 06:08:07 +00:00
Clean up tests and examples (#86)
2017-10-26 21:19:30 +00:00
querySpec :: TestHelpers.Test
Improve and simplify APIs (#68)
2017-09-26 06:08:07 +00:00
querySpec = Spec.describe "Query" do
readSpec
Reference in New Issue Copy Permalink