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
Is your feature request related to a problem? Please describe.
The most common place to use is when trying to update the updatedByUser field, which in that case we would probably want to use the value of auth().id
Describe the solution you'd like
I'm not sure about the syntax but maybe a new operator @updatedBy or @updatedValue that can look like that: @updatedBy/@updatedValue(auth().id)
Describe alternatives you've considered
You can deliever the user id in frontend, but it's not secured and redundant.
In case of using automatic server CRUD using RPCHandler/RestAPIHandler, it's very hard to think about alternative, one of them is to check the body query sent from user, and check if the schema we are about to update has fixed keywords like createdByUser, and if so, to inject to the query (based on the protocol - rpc/rest api) also the createdByUser - this should work but a bit hard to implement and also prone to mistakes in case you change the attributes of your model
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The most common place to use is when trying to update the updatedByUser field, which in that case we would probably want to use the value of
auth().id
Describe the solution you'd like
I'm not sure about the syntax but maybe a new operator
@updatedBy
or@updatedValue
that can look like that:@updatedBy/@updatedValue(auth().id)
Describe alternatives you've considered
You can deliever the user id in frontend, but it's not secured and redundant.
In case of using automatic server CRUD using RPCHandler/RestAPIHandler, it's very hard to think about alternative, one of them is to check the body query sent from user, and check if the schema we are about to update has fixed keywords like
createdByUser
, and if so, to inject to the query (based on the protocol - rpc/rest api) also the createdByUser - this should work but a bit hard to implement and also prone to mistakes in case you change the attributes of your modelThe text was updated successfully, but these errors were encountered: