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
In a project I'm working on we won't need the id, created_at and updated_at columns to be includes in the properties column upon a create action. This can be derived from the other columns of the same activity record. We now have now set the logExcept() for every model but we'll have to remember to set it every time we create a new models.
Would you be open for a PR that allows a config option log_except which contains an array of columns that will never be logged.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In a project I'm working on we won't need the id, created_at and updated_at columns to be includes in the properties column upon a create action. This can be derived from the other columns of the same activity record. We now have now set the logExcept() for every model but we'll have to remember to set it every time we create a new models.
Would you be open for a PR that allows a config option
log_except
which contains an array of columns that will never be logged.A full example:
Beta Was this translation helpful? Give feedback.
All reactions