Avoids recording repeated activities.

[solomon-ochepa]

Avoids recording repeated activities.

Use case:

Tracking access to the user dashboard, for instance, on each refresh, a record will be saved to the database.

Solution:

The system will check the last record, and if it matches the new record, it will return false, preventing the duplicate record from being saved.

[Gummibeer]

No underlying issue attached and no use case description or anything what kind of problem this should solve: closed ❌

[solomon-ochepa]

No underlying issue attached and no use case description or anything what kind of problem this should solve: closed ❌

I discover the issue and choose to create a fix for it since I can.

Nevertheless, the title is clear and descriptive enough.

You should have asked and waited for a response, instead of closing the PR instantly without caring what problem it fixed.

[solomon-ochepa]

I've updated the description. Please check.

[Gummibeer]

Just wrap your outer code in https://github.com/spatie/once for example.
That's absolutely nothing this package should and will handle. As what makes an activity unique and for how long and if duplicates are wanted or not is different per app.

[solomon-ochepa]

Just wrap your outer code in https://github.com/spatie/once for example. That's absolutely nothing this package should and will handle. As what makes an activity unique and for how long and if duplicates are wanted or not is different per app.

You can't use that package to test repeated action scenarios. Why not test the case study I provided instead?

Case:

Log user access to the Dashboard page.

Result:

Every time the user refreshes the Dashboard, a new entry will be recorded, repeatedly.

Solution:

Only the first entry should be recorded. On each subsequent refresh, the model should check if the last log is the same as the incoming record, if the same the transaction should be aborted, or updated.