summaryrefslogtreecommitdiff
path: root/api.lisp
AgeCommit message (Collapse)Author
2023-01-07First Draft of hero creation and loginGrant Shoshin Shangreaux
2023-01-07Revert "Add: serialization for Heroes and dnd.api package"Grant Shoshin Shangreaux
This reverts commit 72bcf7e66269af588d9daa9064de23d257cbd053.
2023-01-07Revert "Refactor: to embrace the new dnd.api package more fully"Grant Shoshin Shangreaux
This reverts commit ab0d667b3776786461d15112b648aafc3f00280f.
2022-12-28Refactor: to embrace the new dnd.api package more fullycolin
The defendpoint* form installs the new endpoint into the default app, which is just hte name of the package. In this case, the GET "/heroes" endpoint is installed into the app called 'dnd.api:dnd.api It is a bit wierd but that's the full name of the app that you'll need to install into your http server instances. I moved *dnd-arena* to the dnd package b/c the site/view app will also be installed there. In addition, the conjure-arena function should also be part of the "top level" dnd package. In the package.lisp file, I reformatted the file a bit for legibility. More importantly, I exported dnd.api and init-db from the dnd.api package. In particular, the second export sends a clear signal that the view/site code will not touch the model at all.
2022-12-28Add: serialization for Heroes and dnd.api packageGrant Shoshin Shangreaux
2022-12-28Rename: dungeons-and-deadlines to dndcolin
2022-12-26Add: a basic json endpoint to return hall-of-fame dataColin Okay