h*<85      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~0.1.0.3 Safe-Inferred(c) Justin Le 2019BSD3 justin@jle.im experimental non-portable Safe-Inferred%&)*9:; H servant-cliStructure for a parser of a given value that may use items from captures and arguments. servant-clipath components servant-clicaptures servant-cliEndpoint arguments and body.! servant-cliCaptures can be a single capture leading to the next level, or a multi-capture leading to an endpoint action." servant-cliA map of endpoints associated with methods, paired with an optional "raw" endpoint.& servant-cli Interpret an ( as something that can be given repeatedly an arbitrary number of times.( servant-cli%Captures are interpreted as arguments. servant-cli+Query parameters are interpreted as options5 servant-cliHow to "read" an option.D servant-cli Convert a 0 into a command line argument parser, from the optparse-applicative library. It can be run with .It takes options on how the top-level prompt is displayed when given "--help"; it can be useful for adding a header or program description. Otherwise, just use .E servant-cliLow-level implementation of D.F servant-cli Combine two 8s in an either-or fashion, favoring the left hand side.G servant-cliShift by a path component.H servant-cli+Add a command-line option to all endpoints.I servant-cli4Add notes to the beginning of a documentation level.J servant-cliAdd a single argument praser.K servant-cli Add a repeating argument parser.L servant-cli$Add a request body to all endpoints.If done more than once per endpoint, it runs *both* parsers; however, we can only send one request body, so this is undefined behavior as a client.M servant-cliCreate an endpoint action.N servant-cliCreate a raw endpoint.O servant-cliHelper to lift a & into something that can be used with 4.P servant-cliHelper to lift an optional ' into something that can be used with 4.Q servant-cliAn 4 that is on-or-off.S servant-cli Combine two s, preferring the left hand side for conflicts. If the left hand has a capture, the right hand's components are ignored. If the left hand has a raw endpoint, the right hand's endpoints are ignored.U servant-cli Combine two "s, preferring the left hand side for conflicts. If the left hand has a raw endpoint, the right hand's endpoints are ignored.D servant-cliThe  to convert. servant-cli-Modify how the top-level prompt is displayed.E servant-cli add helper servant-cli root path servant-climodify top level55678./10234()*+,-&'! "#$%>?ABC@DEFGLHJKIMNOPQ55678./10234()*+,-&'! "#$%>?ABC@DEFGLHJKIMNOPQF3G4H4I4J4K4L4(c) Justin Le 2019BSD3 justin@jle.im experimental non-portable Safe-Inferred=[ servant-cliA helper class for defining directly how to parse request bodies. This allows more complex parsing of bodies.:You need an instance of this for every type you use with .] servant-cli&Default implementation that expects a --data option.] servant-clitype specification servant-cliparser[\][\](c) Justin Le 2019BSD3 justin@jle.im experimental non-portable Safe-Inferred%&01*%d servant-cli=Contains a subcontext that can be descended down into using d . Mirrors   .Useful for when you have multiple items with the same name within a context; this essentially creates a namespace for context items.f servant-cliTypeclass defining how each API combinator influences how a server can be interacted with using command line options.4Note that query parameters and captures all require  servant-docs: annotation instances, to allow for proper help messages.Unless you are adding new combinators to be used with APIs, you can ignore this class.g servant-cliThe parsed type of the client request response. Usually this will be a bunch of nested 3s for every API endpoint, nested according to the  s in the API.h servant-cliThe type of a data structure to conveniently handle the results of all pontential endpoints. This is useful because it is often tedious to handle the bunch of nested s that g has.It essentially lets you specify how to sort each potential endpoint's response into a single output value.'Usually this will be a bunch of nested 0s which handle each endpoint, according to the ,s in the API. It mirrors the structure of  and   .Used with functions like  .i servant-cliCreate a structure for a command line parser, which parses how to modify a  and perform an action, given an API and underlying monad. Only meant for internal use; should be used through   instead.Takes a  of actions to generate required items that cannot be passed via the command line (like authentication). Pass in  if no parameters are expected. The actions will only be run if they are needed.j servant-cli"Handle all the possibilities in a g, by giving the appropriate h.k servant-cliData family associating API combinators with contexts required to run them. These typically will be actions in m that fetch/generate the required data, and will only be "run" if the user selects an endpoint that requires it through the command line interface.s servant-cliAllows you to access ds inside a context. servant-cli'Helper for mapping parameter generators servant-cli!Two-argument function compositiont servant-cliAdd l to the required context, meaning it must be provided to allow the client to generate authentication data. The action will only be run if the user selects this endpoint via command line arguments.Please use a secure connection!u servant-cliAdd n to the required context, meaning it must be provided to allow the client to generate authentication data. The action will only be run if the user selects this endpoint via command line arguments.Please use a secure connection!y servant-cli4Asks for method as a command line argument. If any  exists at the same endpoint, it can only be accessed as an extra RAW; subcommand (as if it had an extra path component labeled RAW).z servant-cli is displayed during --help7 when it is reached while navigating down subcommands.{ servant-cli is displayed during --help7 when it is reached while navigating down subcommands.| servant-cliUsing ! has no affect on CLI operations.} servant-cliA  in the middle of a path is interpreted as a command line argument, prefixed with "header". For example,  "foo"  is an option for  --header-foo. Like for , arguments are associated with the action at their endpoint. After entering all path components and positional arguments, the parser library will begin asking for arguments.~ servant-cli As a part of ctx, asks for a streaming source a. servant-cli2Same semantics in parsing command line options as . servant-cliFinal actions are the result of specifying all necessary command line positional arguments.All command line options are associated with the final action at the end of their endpoint/path. They cannot be entered in "before" you arrive at your final endpoint.If more than one action (under a different method) exists under the same endpoint/path, the method (GET, POST, etc.) will be treated as an extra final command. After that, you may begin entering in options. servant-cli0Request body requirements are interpreted using [.Note if more than one  is in an API endpoint, both parsers will be "run", but only the final one will be used. This shouldn't be an issue, since multiple 5s in a single endpoint should be undefined behavior. servant-cli;Query flags are interpreted as command line flags/switches. arguments are associated with the action at their endpoint. After entering all path components and positional arguments, the parser library will begin asking for arguments.Note that these require  instances from  servant-docs(, to provide appropriate help messages. servant-cli9Query parameters are interpreted as command line options. arguments are associated with the action at their endpoint. After entering all path components and positional arguments, the parser library will begin asking for arguments.Note that these require  instances from  servant-docs(, to provide appropriate help messages. servant-cliA  is interpreted as arbitrarily many command line arguments. If there is more than one final endpoint method, the method must be given as a command line option before beginning the arguments. servant-cliA ? is interpreted as a positional required command line argument.Note that these require  instances from  servant-docs(, to provide appropriate help messages. servant-cli2A path component is interpreted as a "subcommand". servant-cliUsing alternation with  provides an  between the two results. servant-cli will always fail to parse.The branch ending in 5 will never be return, so if this is combined using /, the branch will never end up on the side of . One can use $ to handle this branch as a part of h. servant-cliDescend down a subcontext indexed by a given name. Must be provided when parsing within the context.Useful for when you have multiple items with the same name within a context; this essentially creates a namespace for context items.fghjikqpnlromdesfghjikqpnlromdes(c) Justin Le 2019BSD3 justin@jle.im experimental non-portable Safe-Inferred017 servant-cli A version of  that can be used if the API requires any external context to generate runtime data. servant-cli A version of  that can be used if the API requires any external context to generate runtime data. servant-cli A version of  that can be used if the API requires any external context to generate runtime data. servant-cli A version of  that can be used if the API requires any external context to generate runtime data. servant-cli-Create a structure for a command line parser.This can be useful if you are combining functionality with existing optparse-applicative parsers. You can convert a  to a  using D. servant-cliCreate a structure for a command line parser, producing results according to a h. See  for more information.This can be useful if you are combining functionality with existing optparse-applicative parsers. You can convert a  to a  using D. servant-cli>Parse a servant client; the result can be run. The choice of m gives the backend you are using; for example, the default GHC servant-client backend is .:Returns the request response, which is usually a layer of  for every endpoint branch. You can find the response type directly by using typed holes or asking ghci with :t or #:kind! forall m. CLIResult m MyAPI/. Because it might be tedious handling nested s, see  for a way to handle each potential branch in a convenient way.Takes options on how the top-level prompt is displayed when given "--help"; it can be useful for adding a header or program description. Otherwise, just use . servant-cliParse a server client, like . However, instead of that client action returning the request response, instead use a h to handle every potential request response. It essentially lets you specify how to sort each potential endpoint's response into a single output value.The handler is usually a  for every endpoint branch. You can find it by using typed holes or asking ghci with :t or ):kind! forall m r. CLIHandler m MyAPI r.Takes options on how the top-level prompt is displayed when given "--help"; it can be useful for adding a header or program description. Otherwise, just use . servant-cli Client monad servant-cliAPI servant-cli Extra context servant-cli Client monad servant-cliAPI servant-cli Extra context servant-cliHandler servant-cliAPI servant-cli Client monad servant-cli Extra context servant-cliOptions for top-level display servant-cliAPI servant-cli Client monad servant-cli Extra context servant-cliOptions for top-level display servant-cliHandler servant-cli Client monad servant-cliAPI servant-cli Client monad servant-cliAPI servant-cliHandler servant-cliAPI servant-cli Client monad servant-cliOptions for top-level display servant-cliAPI servant-cli Client monad servant-cliOptions for top-level display servant-cliHandler3fghjkqpnlromdesD[\] 3fghjkqpnlromdesD[\]  !!"#$%&'()**+,-.//012345667789:;<<=>?@ABCDEFGHIJKKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmno  pqrstuvwxyz{|}~  *servant-cli-0.1.0.3-LuyfEtyaZWHA9ot69TBjcT Servant.CLIServant.CLI.Internal.PStructServant.CLI.ParseBodyServant.CLI.HasCLI servant-cliPaths_servant_cli Servant.APIReqBodyServant.Server NamedContextServerTparseHandleClientcliPStructWithContextServant.API.HeaderHeaderServant.ClientClientM:<|>(servant-docs-0.13-AJTUkh4CwUuG7BZHZZQscIServant.Docs.Internal ParamKindNormalListFlagDocAuthentication _authIntro_authDataRequired DocQueryParam _paramName _paramValues _paramDesc _paramKind DocCapture _capSymbol_capDesc ToAuthInfo toAuthInfo ToCapture toCaptureToParamtoParamPStructpsInfo psComponents psCaptures psEndpointsEndpointepStructCaptures EndpointMapEPMepmGivenepmRawMultiArgArgargNameargDescargMetaargReadOptoptNameoptDescoptMetaoptValsoptReadOptRead ORRequired OROptionalORSwitch$fFunctorPStruct$fFunctorEndpointMap$fFunctorEndpoint $fFunctorArg $fFunctorOptPStructFpsInfoF psComponentsF psCapturesF psEndpointsF structParser structParser_branch$:>?:>note#:>##:>%:>endpoint rawEndpoint orRequired orOptionalorSwitch$fMonoidPStruct$fSemigroupPStruct$fMonoidEndpointMap$fSemigroupEndpointMap$fCorecursivePStruct$fRecursivePStruct$fFunctorPStructF$fFoldablePStructF$fTraversablePStructF ParseBody parseBodydefaultParseBody$fParseBodyDouble$fParseBodyFloat$fParseBodyInteger$fParseBodyInt$fParseBodyText$fParseBodyText0HasCLI CLIResult CLIHandlercliPStructWithContext_ cliHandler ContextForGenBasicAuthDatagenBasicAuthData GenAuthReq genAuthReqNC GenStreamBody genStreamBodydescendIntoNamedContext$fHasCLIm:>ctx$fHasCLIm:>ctx0$fHasCLIm:>ctx1$fHasCLIm:>ctx2$fHasCLIm:>ctx3$fHasCLImRawctx$fHasCLIm:>ctx4$fHasCLIm:>ctx5$fHasCLIm:>ctx6$fHasCLIm:>ctx7$fHasCLIm:>ctx8$fHasCLImStreamctx$fHasCLImVerbctx$fHasCLIm:>ctx9$fHasCLIm:>ctx10$fHasCLIm:>ctx11$fHasCLIm:>ctx12$fHasCLIm:>ctx13$fHasCLIm:>ctx14$fHasCLIm:<|>ctx$fHasCLImEmptyAPIctx$fHasCLImWithNamedContextctxcliHandlePStructWithContextparseClientWithContextparseHandleClientWithContext cliPStructcliHandlePStruct parseClientversion getBinDir getLibDir getDynLibDir getDataDir getLibexecDirgetDataFileName getSysconfDir4optparse-applicative-0.18.1.0-5cbl2zXi6SE2pC3wd7rg7UOptions.Applicative.Extra execParserbaseGHC.BasememptyOptions.Applicative.TypesReadM Data.EitherEither%servant-0.20.1-BiK1zGqVOdD1IuFZD8giktServant.API.Alternative/servant-client-core-0.20-BOsbllbFOVgCb7XYKc0o1tServant.Client.Core.HasClientClientServant.Client.Core.RequestRequestF#vinyl-0.14.3-KQ7sRVlqPg7LE5JFUXHC11Data.Vinyl.CoreRecRNil withParamM.:Servant.API.VerbsVerbServant.API.Description DescriptionSummary'http-types-0.12.4-7ravU9ZeEhYD9G3h69uf3Network.HTTP.Types.Version HttpVersionHeader'ghc-prim GHC.TypesIntServant.API.QueryParam QueryParam'Servant.API.ReqBody QueryFlagServant.API.Capture CaptureAllCaptureServant.API.EmptyEmptyAPIabsurdParser