MeowcaTheoRange/TrollCallAPIs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
A set of TrollCallNotAgain-equivalent API hooks, made to let developers create third-party apps for the TrollCall service.
6 commits 1 branch 0 tags 7.6 MiB
TypeScript 94.4%
CSS 5.6%
Find a file
MeowcaTheoRange 6a5a85c773 permissions!
2023-06-30 20:35:15 -05:00
.vscode OK, I think that's enough 2023-06-19 00:16:00 -05:00
src permissions! 2023-06-30 20:35:15 -05:00
.eslintrc.json Move to Next.js 2023-06-26 21:56:32 -05:00
.gitignore Move to Next.js 2023-06-26 21:56:32 -05:00
.prettierrc permissions! 2023-06-30 20:35:15 -05:00
next.config.js Move to Next.js 2023-06-26 21:56:32 -05:00
package-lock.json Move to Next.js 2023-06-26 21:56:32 -05:00
package.json Move to Next.js 2023-06-26 21:56:32 -05:00
README.md Update README.md 2023-06-19 00:29:20 -05:00
tsconfig.json Move to Next.js 2023-06-26 21:56:32 -05:00

README.md

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/user/.../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