-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
feat(report): add report system #61
Conversation
Great question: A normal account should very much be able to access report! For creating reports, that is, and monitoring the status of their reports. A policy defining the creator of a report to be the only one able to access it must be defined of course. How admins work with reports is another topic. We could set up email notifications or build an admin dashboard. Notifications make more sense for now, I'd say. |
Notifications are a solution yes, but we still need to manage these reports, right? So we need some kind of interface. Unless we want to manually fiddle with the database. |
Let's fiddle with the database until there are some reports or reports that need to be managed by a non-admin. |
feat(report): add created column
Comment for column `created` was missing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the collaboration! LGTM 💚
🎉 This PR is included in version 3.5.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Since we need a report system I added a table for that.
The policies are still missing and will be implemented soon.Do we need a new role for the report system? Since a normal account shouldn't be able to access the reports, right?