11 Commits

Author SHA1 Message Date
2147d7ad5e Redo simulations lifecycle ()
## Why

The current way of creating and deleting simulations doesn't scale for big instances. We cannot generate 50 simulations every time a guest confirms attendance, and we should not delete existing valuable simulations. For example, if a guest confirms attendance and declines right after, previously generated simulations should still be valid.

## What

In this PR we are introducing a series of changes that make simulations management easier:

1. We're removing the automatic creation of simulations.
2. Simulations are not removed anymore, neither manually nor automatically.
3. A new endpoint has been defined to create simulations on demand.
4. A digest property has been defined to determine whether a simulation is still valid (meaning there have not been any change in the list of guests involved).

Reviewed-on: 
Co-authored-by: Manuel Bustillo <bustikiller@bustikiller.com>
Co-committed-by: Manuel Bustillo <bustikiller@bustikiller.com>
2025-01-26 12:53:21 +00:00
8c12884212 Add copyright notice 2025-01-23 21:34:23 +00:00
6cead51bb9 Remove all copyright notices to force recreation 2025-01-23 22:29:26 +01:00
74ca20d3e8 Add copyright notice 2025-01-23 21:18:12 +00:00
91bbae1c63 Add copyright notice 2025-01-13 20:38:47 +00:00
e20a366410 Update copyright assignment to cover 2025 and include all contributors 2025-01-13 21:37:02 +01:00
55e6cfcd36 Fix order of Ruby's magic string comment and Copyright assignment 2024-12-28 18:37:47 +01:00
2fc8a6340b Run Rubocop autocorrect on spec/ 2024-12-28 18:07:40 +01:00
3bfe889747 Redo TablesArrangements#show to display arrangement ID and discomfort breakdown 2024-12-16 18:52:34 +01:00
5cbc81c498 Add copyright notice 2024-12-08 13:02:08 +00:00
9d90ade40c Document tables arrangements controller 2024-12-08 14:00:53 +01:00