Heyo! When creating a user from the client, it currently wants the user ID to use from the client. I don't think I need to explain why this is maybe a bad idea (Don't let the client do literally anything that's not needed.) Is there anyway I can leave AppWrite to do the generating?
import ID.unique() and use that for the user id.
Well yeah, but I want that to happen on the AppWrite server instead of on the client
pass the literal string "unique()"
This actually generates the ID client-side now
Gotcha, thank you
but, then again, they could not pass that string and pass whatever they want instead.
If you really care about it, don't call createDocument() client-side. Expose a function, instead
This is mostly just to stop people who have no idea what they're doing from poking at my code, not really a security measure lol
so what's the problem with using ID.unique()?
It's not really per say a problem, I've just watched way too many people go to the network tab, spot that it's sending the ID to be created and leaving creative messages in there, only to request support 5 seconds later. This won't stop them, but it'll hopefully less annoying.
Recommended threads
- All function deployments fail (node 18-2...
Error: bash: /usr/local/server/helpers/build-cache.sh: No such file or directory Sidecar error: Build archive was not created at /mnt/code/code.tar.gz Scope: ...
- Why does this happen?
`AppwriteException: general_argument_invalid, Invalid `secret` param: Value must be a valid string and at least 1 chars and no longer than 256 chars (400)` the...
- Database Write Limits hit
Hello Appwrite Admins, I'm a GitHub Education user, and about a week ago, my database was really badly optimized, resulting in about 600k writes in a single day...