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
Similar (but I think less common than) #26 it would be useful if resources linked the creator and editor to the resource being updated or created. I think resources can derive the active user based on the session given that we always use a consistent model for session -> acount -> user, but not 100% sure.
Here as well this would be configurable based on a flag.
The text was updated successfully, but these errors were encountered:
I wonder if it wouldn't be better/possible to add such a feature to mu-authorization instead. My main concern is that although automation via resources/the frontend is great, data is also created in services where that automation isn't going to be present. I imagine it'd be very easy to accidentally forget to set these fields in a service. If such a thing was instead handled at the base layer that all queries pass through, it could be added enabled for all cases.
Similar (but I think less common than) #26 it would be useful if resources linked the creator and editor to the resource being updated or created. I think resources can derive the active user based on the session given that we always use a consistent model for session -> acount -> user, but not 100% sure.
Here as well this would be configurable based on a flag.
The text was updated successfully, but these errors were encountered: