12 replies

Why calling an action from a client is an anti-pattern?

❔Advice

When then is good to use an action from client?
If we need to write a mutation based on the response of a third party API, that's probably the unique case when we can call the action directly from the client?

Context: A note in the docs

Note: In most cases calling an action directly from a client is an anti-pattern. Instead, have the client call a mutation which captures the user intent by writing into the database and then schedules an action:

Note: In most cases calling an action directly from a client is an anti-pattern. Instead, have the client call a mutation which captures the user intent by writing into the database and then schedules an action:

Convex Community•2y ago•

12 replies

cosmo

Why calling an action from a client is an anti-pattern?

❔Advice

Note: In most cases calling an action directly from a client is an anti-pattern. Instead, have the client call a mutation which captures the user intent by writing into the database and then schedules an action:

Note: In most cases calling an action directly from a client is an anti-pattern. Instead, have the client call a mutation which captures the user intent by writing into the database and then schedules an action:

Continue the conversation

Join the Discord to ask follow-up questions and connect with the community

Convex Community

Join the Convex Discord! Explore Convex, the backend platform that keeps your app in sync.

16,164 Members

Join

Why calling an action from a client is an anti-pattern?

Why calling an action from a client is an anti-pattern?

Continue the conversation

Convex Community

Continue the conversation

Convex Community

Similar Threads