Îõ³h&¿24      !"#$%&'()*+,-./0123None  %'(/8>?ÀÁÂÎÔÖ×Ùéíîñ< nri-httpA ' can come back a couple different ways:# ”@ you did not provide a valid URL.& ”@ it took too long to get a response.7 ”@ the user turned off their wifi, went in a cave, etc. = ”@ a response arrived, but the status code indicates failure. . ”@ a response arrived with a nice status code!ÜThe type of the body depends on whether you use expectStringResponse or expectBytesResponse. nri-httpA  can fail in a couple of ways: ' means you did not provide a valid URL. * means it took too long to get a response.; means the user turned off their wifi, went in a cave, etc.Æ means you got a response back, but the status code indicates failure.ó means you got a response back with a nice status code, but the body of the response was something unexpected. The 4è in this cse is the debugging message that explains what went wrong with your JSONT decoder or whatever.nri-http'Logic for interpreting a response body.nri-http!Represents the body of a Request.nri-http*An HTTP header for configuration requests.nri-httpA custom request.nri-httpThe request method, like GET or PUT.nri-httpA list of request headers.nri-httpThe url, like " https://fishes.com/salmon".nri-httpThe request body.nri-httpÃThe amount of microseconds you're willing to wait before giving up.nri-http6The type of response you expect back from the request.nri-http#A handler for making HTTP requests.+   56789:;<=>?@ABNone  %'(/8>?ÀÁÂÎÔÖ×Ùéíîñnri-http Create a  for making HTTP requests.nri-http;Third party libraries that make HTTP requests often take a C8. This helper allows us to call such a library using a .2The benefit over using this over using a separate C$ for the external library, is that É will ensure HTTP requests made by the external library will get logged.nri-httpLike , but runs in D. nri-http Create a GET request.!nri-http Create a POST request."nri-http Create a Header.#nri-httpýCreate an empty body for your Request. This is useful for GET requests and POST requests where you are not sending any data.$nri-http,Put some string in the body of your Request.ÓThe first argument is a MIME type of the body. Some servers are strict about this!%nri-httpøPut some JSON value in the body of your Request. This will automatically add the Content-Type: application/json header.&nri-http Put some Bytes in the body of your Request. This allows you to use ByteString to have full control over the binary representation of the data you are sending.ìThe first argument is a MIME type of the body. In other scenarios you may want to use MIME types like image png or image jpeg instead.'nri-httpCreate a custom request.(nri-http$Expect the response body to be JSON.)nri-http!Expect the response body to be a 4.*nri-httpÇExpect the response body to be whatever. It does not matter. Ignore it!+nri-http Expect a Response with a 4 body.,nri-http Expect a Response with a E body-  !"#$%&'()*+,- !' "#$%&()*+, None  %'(/8>?ÀÁÂÆÎÔÖ×ÙéíîñÛ-nri-http–A stub for a single request type. If your test body can perform multiple different kinds of http requests, you'll want one of these per request type..nri-http Create a -./nri-http´Stub out http requests in a bit of code. You can use this if you don't want your tests to make real http requests, and to listen in on the http requests it is attempting to make./¢ takes a function that it calls instead of making a real http request. That function should return the response string and a optionally some information about the http request. You'll get back the information collected for each outgoing http request so you can run assertions against it. ¸test "Stubbed HTTP requests" <| \_ -> do urlsAccessed <- Http.Mock.stub [mkStub (\req -> Task.succeed (Http.url req, "Response!" :: Text))] ( \http -> Expect.succeeds <| do _ <- Http.get http "example.com/one" Http.expectText _ <- Http.get http "example.com/two" Http.expectText Task.succeed () ) urlsAccessed |> Expect.equal ["example.com/one", "example.com/two"]0nri-httpØRead the body of the request as text. Useful to check what data got submitted inside a / function.This will return F+ if the body cannot be parsed as UTF8 text.1nri-httpØRead the body of the request as json. Useful to check what data got submitted inside a / function.9This will return an error if parsing the JSON body fails.2nri-httpÙRead the body of the request as bytes. Useful to check what data got submitted inside a / function.3nri-httpÐRead a header of the request. Useful to check what data got submitted inside a / function.This will return F5 if no header with that name was set on the request.-./0123/-.3012None  %/8>?ÀÁÂÎÖ×Ùéíîñ%GHIJKLMNÏ      !"#$%&'()*+,-./01234567889:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWØnri-http-0.2.0.0-inplaceHttp Http.Mock Http.InternalPaths_nri_httpMetadatametadataStatusCodemetadataStatusTextmetadataHeadersResponseBadUrl_Timeout_ NetworkError_ BadStatus_ GoodStatus_ErrorBadUrlTimeout NetworkError BadStatusBadBodyExpectBodyHeaderRequestmethodheadersurlbodytimeoutexpectHandlerhandlerwithThirdPartywithThirdPartyIOgetpostheader emptyBody stringBodyjsonBody bytesBodyrequest expectJson expectTextexpectWhateverexpectTextResponseexpectBytesResponseStubmkStubstub getTextBody getJsonBody getBytesBody getHeadernri-prelude-0.6.0.6-inplaceTextExpectBytesResponseExpectTextResponseExpectWhatever ExpectText ExpectJsonbodyContentType bodyContentsunHeaderhandlerWithThirdPartyIOhandlerWithThirdPartyhandlerRequest*http-client-0.6.4.1-7w5cAPnFh44JUJQMqBIwLvNetwork.HTTP.Client.TypesManagerghc-prim GHC.TypesIObytestring-0.10.12.0Data.ByteString.Internal ByteStringbase GHC.MaybeNothingversiongetDataFileName getBinDir getLibDir getDynLibDir getDataDir getLibexecDir getSysconfDir