Forbid cancelling/interacting with past events

[spreeni]

I realized that cancelling and a couple other actions were still technically possible on past events.

New changes:

• Forbid following actions for past events:
  • cancelling event
  • request community invite
  • transfer event
  • set event subscription
  • set event attendance
  • invite event organizer
  • remove event organizer
• Disable edit, cancel and attendance buttons in frontend for past events

Backend checklist

• [x] Formatted my code by running ruff check --select I --fix . && ruff check . && ruff format . in app/backend
• [ ] Added tests for any new code or added a regression test if fixing a bug
• [x] All tests pass
• [x] Run the backend locally and it works
• [x] Added migrations if there are any database changes, rebased onto develop if necessary for linear migration history

Web frontend checklist

• [x] Formatted my code with make format
• [x] There are no warnings from make lint
• [x] There are no console warnings when running the app
• [x] Added any new components to storybook
• [x] Added tests where relevant
• [x] All tests pass
• [x] Clicked around my changes running locally and it works
• [x] Checked Desktop, Mobile and Tablet screen sizes

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
couchers	✅ Ready (Inspect)	Visit Preview	Jun 13, 2024 8:47pm

[spreeni]

I did not run the frontend tests in my ignorance 🤦 - all the sample event dates in the tests are in the past, will adjust it later.