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
Hi all! I hope everyone is well and would firstly like to offer my thanks for creating such an easy-to-implement package.
In using it I have really missed a feature to update existing activity in the logs; I haven't been able to find a way to update properties on an existing activity item.
We have a booking system and when we create a booking we log its creation, as well as its start and end times as activities (booking_start and booking_end), and we also allow the user to update a booking. Now, we do also log these updates and that works splendidly, it's just the start and end activities that remain as they were set.
It'd be awesome if there were a way I could do something like:
Alas, the documentation (which, again, is excellent) doesn't seem to mention such a method :(
I am aware of the possibility that such functionality isn't quite within what this package is for - logging what happens to a model rather than the model itself doing something. So, if that is the case and I'm barking up the wrong tree, please let me know!
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
-
Hi all! I hope everyone is well and would firstly like to offer my thanks for creating such an easy-to-implement package.
In using it I have really missed a feature to update existing activity in the logs; I haven't been able to find a way to update properties on an existing activity item.
We have a booking system and when we create a booking we log its creation, as well as its start and end times as activities (
booking_start
andbooking_end
), and we also allow the user to update a booking. Now, we do also log these updates and that works splendidly, it's just thestart
andend
activities that remain as they were set.It'd be awesome if there were a way I could do something like:
Alas, the documentation (which, again, is excellent) doesn't seem to mention such a method :(
I am aware of the possibility that such functionality isn't quite within what this package is for - logging what happens to a model rather than the model itself doing something. So, if that is the case and I'm barking up the wrong tree, please let me know!
Beta Was this translation helpful? Give feedback.
All reactions