Event data used by the table is cached - but this is annoying for testing and active usage. We should look into ways to manually invalidate/regenerate cache during event creation.
Note: Cache invalidation logic should NOT be contained within the event creation page itself. Cache invalidation should be contained within the function that creates the event itself, such that the logic is centralized as close to where it occurs, when possible.
Event data used by the table is cached - but this is annoying for testing and active usage. We should look into ways to manually invalidate/regenerate cache during event creation.
Note: Cache invalidation logic should NOT be contained within the event creation page itself. Cache invalidation should be contained within the function that creates the event itself, such that the logic is centralized as close to where it occurs, when possible.