Repository navigation
HasActivity trait #1458
Unanswered
SpitsAdmin
asked this question in
Q&A
Replies: 1 comment 1 reply
|
Your reading sounds right to me: if The distinction is:
So a combined trait would normally be expected to expose both sides: $model->activitiesAsSubject()
$model->actionsAsCauser() // or whatever the package names this relationIf v5 docs say
I would open this as a small docs/code mismatch with the exact expectation:
That framing should make it easy for the maintainers to confirm whether this is intentional API design or a bug. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hey,
Small question about the new V5.
As i understand per the docs the
HasActivitytrait combinesCausesActivity&LogsActivityto get all the activitiesBut when i look at the trait class it only implements
$this->activitiesAsSubjectso wouldnt that meanCausesActivityis effectively ignored?https://github.com/spatie/laravel-activitylog/blob/main/src/Models/Concerns/HasActivity.php
All reactions