Skip to content
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

AP: Absences should not be allowed to be duplicate on the database #395

Open
Jayden876212 opened this issue Oct 28, 2024 · 0 comments
Open
Labels
backend API or backend work defect Quality issues risk Security, data privacy, availability, compliance, etc.

Comments

@Jayden876212
Copy link
Collaborator

Jayden876212 commented Oct 28, 2024

For data integrity reasons, the request to update the database should fail if there is already a singular absence (not recurring) there. It doesn't, therefore this is a defect in the back-end data validation logic. This defect was spotted when the corresponding JavaScript was accidentally imported twice and clicking on the calendar would add two absences.

@Jayden876212 Jayden876212 added backend API or backend work defect Quality issues risk Security, data privacy, availability, compliance, etc. labels Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend API or backend work defect Quality issues risk Security, data privacy, availability, compliance, etc.
Projects
None yet
Development

No branches or pull requests

1 participant