úÎ#Q5Mg?      !"#$%&'()*+,-./0123456789:;<=>None,-.;=?@ACHUVXk,ƒ servant-docs-simpleConversion to plaintextservant-docs-simpleConversion to prettyprintservant-docs-simple#Conversion to JSON using Data.Aeson servant-docs-simple6Convert Endpoints into different documentation formats servant-docs-simpleValue representation; see  and $ documentation for a clearer picture servant-docs-simpleList of Parameter-Value pairs servant-docs-simple Single Valueservant-docs-simple7Key-Value pair for endpoint parameters and their values Example 1bAn endpoint is represented as a node, with the route as its parameter and its Details as its value Node "/users/get" <Details> Example 29Details of each endpoint can also be represented as nodesGiven the following: Response '[()] ()bThis can be interpreted as a Response parameter, with a value of 2 Details, Format and ContentTypeIn turn, this:  Format: '[()]9can be interpreted as a Format parameter with a value of '[()].And so parsing Response '[()] () comes together as: ÿžNode "Response" --- Parameter (Details [ Node "Format" -- Parameter --- (Detail "': * () ('[] *)") -- Value | , Node "ContentType" -- Parameter | Value (Detail "()") -- Value | ]) ---servant-docs-simpleBIntermediate documentation structure, a linked-list of endpoints (s) API type: “ type API = "users" :> ( "update" :> Response '[()] () :<|> "get" :> Response '[()] () )Parsed into Endpoints: ÿ” Endpoints [ Node "/users/update" (Details [ Node "Response" (Details [ Node "Format" (Detail "': * () ('[] *)") , Node "ContentType" (Detail "()") ]) ]) , Node "/users/get" (Details [ Node "Response" (Details [ Node "Format" (Detail "': * () ('[] *)") , Node "ContentType" (Detail "()") ]) ]) ]For a breakdown reference For more examples reference chttps://github.com/Holmusk/servant-docs-simple/blob/master/test/Test/Servant/Docs/Simple/Samples.hs Test.Servant.Docs.Simple.Samplesservant-docs-simpleParameter nameservant-docs-simpleParameter value(s)   None,-.;=?@ACHUVXkFµ?servant-docs-simple(Folds an api endpoint into documentation@servant-docs-simpleIWe use this to destructure the API type and convert it into documentationAservant-docs-simple&Folds api endpoints into documentationBservant-docs-simple(Folds list of endpoints to documentation!servant-docs-simple%Flattens API into type level list of Cservant-docs-simple(Folds an api endpoint into documentationDservant-docs-simpleInternal Helper utilities&servant-docs-simple¡Response documentation Terminates here as responses are last parts of api endpoints Note that request type information (GET, POST etc...) is contained here'servant-docs-simpleStream body documentation(servant-docs-simpleRequest body documentation)servant-docs-simpleQuery params documentation*servant-docs-simpleQuery param documentation+servant-docs-simpleQuery flag documentation,servant-docs-simpleRequest header documentation-servant-docs-simpleAuthentication documentation.servant-docs-simple"Basic authentication documentation/servant-docs-simpleVault documentation0servant-docs-simpleSummary documentation1servant-docs-simpleDescription documentation2servant-docs-simple!Request Remote host documentation3servant-docs-simpleIsSecure documentation4servant-docs-simple!Request HttpVersion documentation5servant-docs-simpleCaptureAll documentation6servant-docs-simpleCapture documentation7servant-docs-simpleStatic route documentation@servant-docs-simpleRoute documentationservant-docs-simpleEverything else documentationservant-docs-simple%Generated documentation for the route!"!"None,-.;=?@ACHUVXkM39servant-docs-simple(Write documentation as PlainText to file:servant-docs-simple#Write documentation as JSON to file;servant-docs-simple*Write documentation as PlainText to stdout<servant-docs-simple%Write documentation as JSON to stdout=servant-docs-simple&Convert API type into PlainText format>servant-docs-simple'Convert API type into specified formats9:;<=>=><;:9E       !"#$%&'()*+,-./0123456789:;<=;>?@AB#servant-docs-simple-0.1.0.0-inplaceServant.Docs.Simple.RenderServant.Docs.Simple.ParseServant.Docs.Simple PlainText getPlainTextPretty getPrettyJsongetJson RenderablerenderDetailsDetailNode Endpoints$fToJSONDetails$fToJSONEndpoints$fRenderableJson$fRenderablePretty$fRenderablePlainText $fEqDetails $fShowDetails$fEqNode $fShowNode $fEqEndpoints$fShowEndpoints$fEqJson $fShowJson $fEqPlainText$fShowPlainText HasParsableparse$fHasCollatable[][]$fHasParsableTYPEEmptyAPI$fHasParsableTYPEa$fHasDocumentApiTYPEVerb$fHasDocumentApiTYPE:>$fHasDocumentApiTYPE:>0$fHasDocumentApiTYPE:>1$fHasDocumentApiTYPE:>2$fHasDocumentApiTYPE:>3$fHasDocumentApiTYPE:>4$fHasDocumentApiTYPE:>5$fHasDocumentApiTYPE:>6$fHasDocumentApiTYPE:>7$fHasDocumentApiTYPE:>8$fHasDocumentApiTYPE:>9$fHasDocumentApiTYPE:>10$fHasDocumentApiTYPE:>11$fHasDocumentApiTYPE:>12$fHasDocumentApiTYPE:>13$fHasDocumentApiTYPE:>14$fHasDocumentApiTYPE:>15$fHasCollatable[]:writeDocsPlainText writeDocsJsonstdoutPlainText stdoutJsondocument documentWithHasDocumentApi HasCollatablecollatedocumentEndpointtypeText