Task story:
We need to have detailed logs for stand responsible and for admins and log/store all users actions.
Add logs in next actions:
create stand
edit stand schedule/stand settings/etc.
creating publishers/attaching publishers to congregations
when publishers editing stand and registering in schedule
creating/removing/editing permissions and roles
etc
Ho wo to that:
create new table(users_actions_history or think of better naming) via artisan command and migration file with fields: user_id(with foreign key on users table), action_time/or use default created_at field, payload in json format(pass there all userfull info from each action log), action (slug by - delimeter. Example: stand-register).
create model UsersActions
create service UsersActionsService with adding logs/users_history logic
implement logs logic in all existing endpoints
*new
create endpoint to retrieve logs filtered by date, user_id or date range. FE will create page for admins.
realtek2
commented
1 year ago
Task story: We need to have detailed logs for stand responsible and for admins and log/store all users actions. Add logs in next actions:
Ho wo to that:
users_actions_historyor think of better naming) via artisan command and migration file with fields:user_id(with foreign key onuserstable),action_time/or use defaultcreated_atfield,payloadin json format(pass there all userfull info from each action log),action(slug by-delimeter. Example:stand-register).UsersActionsUsersActionsServicewith adding logs/users_history logic*new
date,user_idor date range. FE will create page for admins.