905ccb9b4b
Make comments the event's host
2025-04-24 13:45:48 +02:00
2f8a9bed0e
There is only ever one account per database
...
So there is no protection in scoping things by account cc @jorgemanrubia
2025-04-12 11:30:28 +02:00
9b4169c7ca
Scope data by account
...
With a single database this problem is not as bad, but it feels
safer to do things right. Also, not everyone in an account has access
to all the bubbles.
2025-04-07 13:09:49 +02:00
a65d7b0397
Don't blow up on missing comment
2025-03-05 16:51:14 +00:00
415e872a2b
Combine concerns
2025-01-14 13:57:48 +00:00
a082eb75f5
Track events for new comments too
2025-01-13 14:21:47 +00:00
85d47a35ab
threadables -> messageables
2024-10-25 15:03:31 -06:00
3db14a117c
Store stage ids in event particulars
2024-10-24 17:36:40 -06:00
c57f18c20c
Materialize abstract thread
...
The domain language is clearer if we just persist a thread. Also rename some models so their purpose is clear.
2024-10-24 17:36:14 -06:00
ad88f90302
Fine not to denormalize user names in events
2024-10-24 15:50:00 -06:00
06ea38a9f7
Denormalize event data
2024-10-23 13:38:00 -06:00
b0565fbf20
Spike workflows
2024-10-21 15:33:30 -06:00
f4b5210ca1
Spike persisted filters
2024-10-16 16:41:11 -06:00
ec7fc75054
Spike events system
2024-10-11 20:14:09 -05:00
Jorge Manrubia