I'm wondering:
Is it possible to block a document create from a server function that is subscribed to the create event?
As means of an additional layer of security?
For my use case it would be to prevent muted users from sending messages during their mute period.
Like a middleware-function? That will be cool but as of now Appwrite function can't go in between some processes.
What you can do now:
- Change permission to a collection - by specific roles for example.
- Delete them right away - this is probably not what you've been looking for.
i typically prevent creation via the API and expose a function to create the document. the function can do any validation and only create the document if validation passes
Okay, makes sense, thanks guys π
create 2 fx. make one for validation and other whatever you like. second fx tigger validation fx and validation fx trigger doc. creation
Recommended threads
- Realtime with multiple connections
I need the Realtime on multiple Collections for diffrent applicational logic. So my question is: Is there a way to have only 1 Websocket connection or do I need...
- Can't login or deploy functions in Appwr...
Hello, since i updatet to the appwrite cli 6.1.0 i can't login or deploy functions with the cli. When i call the command: "appwrite get account --verbose" i ge...
- Create admin user?
I'm not really sure how this is supposed to work, I installed Appwrite through docker-compose and set it up. When I launched the app and went into it, I created...