A set of TrollCallNotAgain-equivalent API hooks, made to let developers create third-party apps for the TrollCall service.
Go to file
MeowcaTheoRange 10ef309270 the regex
2023-10-20 21:24:58 -05:00
.vscode OK, I think that's enough 2023-06-19 00:16:00 -05:00
public Optimization, convert empty strings/arrays to null 2023-10-02 14:30:33 -05:00
src the regex 2023-10-20 21:24:58 -05:00
.eslintrc.json Move to Next.js 2023-06-26 21:56:32 -05:00
.gitignore Fix some stuff for Vercel 2023-09-13 10:49:43 -05:00
.prettierrc permissions! 2023-06-30 20:35:15 -05:00
LICENSE Add NavLink Ads, license, and support flairs 2023-09-09 21:49:36 -05:00
next.config.js Move to Next.js 2023-06-26 21:56:32 -05:00
openapi.yaml Merge with TrollCallFrontEnd 2023-08-29 14:52:02 -05:00
package-lock.json add react-markdown for some reason. 2023-09-25 22:30:34 -05:00
package.json add react-markdown for some reason. 2023-09-25 22:30:34 -05:00
README.md Switch from "Users" to "Clans" 2023-08-07 18:29:30 -05:00
tsconfig.json Messaging update (v0.2) 2023-09-25 12:45:33 -05:00

TrollCallAPIs

A set of TrollCallNotAgain-equivalent API hooks, made to let developers create third-party apps for the TrollCall service.


TrollCall is great, but the merge of the client and server TrollCallNotAgain has with Next.js is problematic. (ahem, Client/Server Hydration and Server Components (those are messy grr))

There are a few issues with the existing APIs as well:

  1. Objects get duplicated if their name/first-name is changed.

Doing this:

PUSH /api/clan/.../troll/name1

{
  ...
  "name": ["name2", ...]
  ...
}

results in this on the database:

trolls/
|- Document {"name": ["name1", ...], ...}
|- Document {"name": ["name2", ...], ...}

which is not good.

  1. More issues that I forgot

They certainly exist