You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to have my services validate that the logged in user can only edit the data that they own. I'm trying to figure out in the docs the most ergonomic way to do this.
I agree. That does sound contradictory 🧐 I think the Service Validations docs are wrong, and personally I'd implement the check you're asking about inside my services. Especially as you then also get the check whenever you call your services from other places and not just directly from graphql.
But @dthyresson is our resident expert on these things, so hopefully he can provide some guidance here 🗺️
Summary and description
my docs version: Redwood 6.0
I'd like to have my services validate that the logged in user can only edit the data that they own. I'm trying to figure out in the docs the most ergonomic way to do this.
On this page: https://redwoodjs.com/docs/directives#when-should-i-use-a-redwood-directive
the docs say to do the check in your service instead.
On the service docs: https://redwoodjs.com/docs/services#service-validations it says you should do this in a validator directive. Is there a contradiction here, or what am I missing?
Are you interested in working on this?
The text was updated successfully, but these errors were encountered: