({\n baseUrl: 'http://localhost:3000/api/sdk',\n})\n\nexport function Data() {\n const { data } = useQuery(client.queries.hello, {\n fn: (hello) => hello(),\n })\n\n return (\n \n {JSON.stringify(data, null, 2)}\n
\n )\n}\n```\n\n# server\n\n## server.makeService\n\nThis enables you to share `context` and `middleware` across fns. Here's an example.\n\n```\n// Make a service\nconst service = server.makeService({\n makeContext: () => ({\n foo: 'bar',\n }),\n middleware: (req, next) => {\n // console.log(req.pathname)\n next()\n }\n})\n```\n\nThen you call\n- `service.makeProcedure()` or `service.makeCommand()`\n- Instead of ~~server~~.makeProcedure() or ~~server.makeCommand()~~\n\n## server.makeRouter\n\nCall this to make the router on the server. That's covered in [Getting Started](#getting-started)\n\n## server.makeQuery\n\nYou should use `server/service.makeProcedure()` to make a GET request. Whether you use `makeQuery` or `makeCommand` doesn't make a difference, but do what's intuitive! Read up on CQRS if you want some reasons why\n\n# client\n\n## client.makeInterface\nSee [Make a dispatcher](#on-the-client-make-a-dispatcher)\n\n## client.call\nSee [Getting Started](#getting-started).\n\nCalling `client.call` with a procedure you created with `makeQuery` will throw a typescript error.\n## client.command\n\nWorks just like `client.call` except you pass it command procedures. \n\n# FAQ\n\n- Waiting on yours!\n\n# To do\n- [ ] More testing\n\n\n","readmeFilename":"README.md","description":""}