Hoogle Search

Within LTS Haskell 24.51 (ghc-9.10.3)

Note that Stackage only displays results for the latest LTS and Nightly snapshot. Learn more.

  1. defaultMakeClientRequest :: Applicative f => BaseUrl -> Request -> f Request

    servant-client Servant.Client

    Create a http-client Request from a servant Request The host, path and port fields are extracted from the BaseUrl otherwise the body, headers and query string are derived from the servant Request Note that Applicative dependency is not really needed for this function implementation. But in the past the return type was wrapped into IO without a necessity breaking the API backward-compatibility. In order to not break the API again it was changed to Applicative so that you can just use something like Data.Functor.Identity without a need to involve IO but still keeping it compatible with the code written when it was typed as IO.

  2. makeClientRequest :: ClientEnv -> BaseUrl -> Request -> IO Request

    servant-client Servant.Client

    this function can be used to customize the creation of http-client requests from servant requests. Default value: defaultMakeClientRequest Note that: 1. makeClientRequest exists to allow overriding operational semantics e.g. responseTimeout per request, If you need global modifications, you should use managerModifyRequest 2. the cookieJar, if defined, is being applied after makeClientRequest is called.

  3. defaultMakeClientRequest :: Applicative f => BaseUrl -> Request -> f Request

    servant-client Servant.Client.Internal.HttpClient

    Create a http-client Request from a servant Request The host, path and port fields are extracted from the BaseUrl otherwise the body, headers and query string are derived from the servant Request Note that Applicative dependency is not really needed for this function implementation. But in the past the return type was wrapped into IO without a necessity breaking the API backward-compatibility. In order to not break the API again it was changed to Applicative so that you can just use something like Data.Functor.Identity without a need to involve IO but still keeping it compatible with the code written when it was typed as IO.

  4. makeClientRequest :: ClientEnv -> BaseUrl -> Request -> IO Request

    servant-client Servant.Client.Internal.HttpClient

    this function can be used to customize the creation of http-client requests from servant requests. Default value: defaultMakeClientRequest Note that: 1. makeClientRequest exists to allow overriding operational semantics e.g. responseTimeout per request, If you need global modifications, you should use managerModifyRequest 2. the cookieJar, if defined, is being applied after makeClientRequest is called.

  5. performRequest :: Maybe [Status] -> Request -> ClientM Response

    servant-client Servant.Client.Internal.HttpClient

    No documentation available.

  6. defaultMakeClientRequest :: Applicative f => BaseUrl -> Request -> f Request

    servant-client Servant.Client.Internal.HttpClient.Streaming

    Create a http-client Request from a servant Request The host, path and port fields are extracted from the BaseUrl otherwise the body, headers and query string are derived from the servant Request Note that Applicative dependency is not really needed for this function implementation. But in the past the return type was wrapped into IO without a necessity breaking the API backward-compatibility. In order to not break the API again it was changed to Applicative so that you can just use something like Data.Functor.Identity without a need to involve IO but still keeping it compatible with the code written when it was typed as IO.

  7. makeClientRequest :: ClientEnv -> BaseUrl -> Request -> IO Request

    servant-client Servant.Client.Internal.HttpClient.Streaming

    this function can be used to customize the creation of http-client requests from servant requests. Default value: defaultMakeClientRequest Note that: 1. makeClientRequest exists to allow overriding operational semantics e.g. responseTimeout per request, If you need global modifications, you should use managerModifyRequest 2. the cookieJar, if defined, is being applied after makeClientRequest is called.

  8. performRequest :: Maybe [Status] -> Request -> ClientM Response

    servant-client Servant.Client.Internal.HttpClient.Streaming

    No documentation available.

  9. performWithStreamingRequest :: Request -> (StreamingResponse -> IO a) -> ClientM a

    servant-client Servant.Client.Internal.HttpClient.Streaming

    TODO: support UVerb (acceptStatus argument, like in performRequest above).

  10. defaultMakeClientRequest :: Applicative f => BaseUrl -> Request -> f Request

    servant-client Servant.Client.Streaming

    Create a http-client Request from a servant Request The host, path and port fields are extracted from the BaseUrl otherwise the body, headers and query string are derived from the servant Request Note that Applicative dependency is not really needed for this function implementation. But in the past the return type was wrapped into IO without a necessity breaking the API backward-compatibility. In order to not break the API again it was changed to Applicative so that you can just use something like Data.Functor.Identity without a need to involve IO but still keeping it compatible with the code written when it was typed as IO.

Page 271 of many | Previous | Next