-
Notifications
You must be signed in to change notification settings - Fork 691
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inherited models don't fire audit events #677
Comments
I've re-opened this as it does pose an interesting issue, so curious what the options are... If you have a model setup like this:
When ever the
However, if you were to do an update on the
This makes sense, in that it was
Even though the record is the same, but the object in which the audit is associated is different, so it means you can't retrieve the audits, and also then means you can't see them against the collection itself. Is there a way to get around this? Perhaps trick Audited into seeing the model name as something different? or perhaps being able to join inherited models somehow when pulling back the audit records? |
I was having a look at that method
Perhaps that can be monkey-patched to pull through associated inherited models too? |
I decided that it makes sense that the inherited model should fire audits against that model and not the parent and moved the logic to the original model with some conditionals instead.
The text was updated successfully, but these errors were encountered: