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

Bug Batch 2 (Backend) #58

Closed
michellelin1 opened this issue Mar 5, 2024 · 1 comment · Fixed by #61
Closed

Bug Batch 2 (Backend) #58

michellelin1 opened this issue Mar 5, 2024 · 1 comment · Fixed by #61
Assignees
Labels

Comments

@michellelin1
Copy link
Member

Instructions

  • Since the Published Schedule table and Catalog table are linked together, we’ve realized that if someone made modifications to an event in the Catalog table, those changes would unintentionally be reflected in events in the Published Schedule table (and we don’t want that since the schedule is supposed to be final). Additionally, you wouldn’t be able to delete a Catalog Event if it was referenced in a Published Schedule row.
  • As a result we decided to
    • Remove the edit button from the Catalog table (comment out the code incase we still want it)
    • Add a new row to Catalog table in the backend to called “hidden”
      • Hidden should be defaulted to false in POST /catalog
      • In GET /catalog, only return rows that are not hidden
      • In DELETE /catalog, if event_id is not referenced at all in the Published Schedule table, delete it like normal. Otherwise, set hidden to true.
  • Additionally, we would like you to modify the foreign key references to day_id in the published_schedule table to delete on cascade.

Acceptance Criteria

  • The edit button is no longer apparent in the catalog table
  • Users can “delete” rows from the Catalog
  • When you delete a day object, all Published Schedule events associated with it are also deleted.

Resources

@h0ethan04
Copy link
Contributor

Additional Acceptance Criteria:

  • Forbidden from adding duplicate days to the day table

@ThatMegamind ThatMegamind linked a pull request Mar 21, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants