 Kevin McConnell
|
dac2611c57
|
Auto-pop bubbles
|
2025-02-12 13:20:05 +00:00 |
|
|
Jason Zimdars
|
f25335ba38
|
Try comment excerpts in notification and event chips
|
2025-02-04 14:04:17 -06:00 |
|
|
Kevin McConnell
|
e6fe7f680d
|
Associate Event with Bubble
It's kind of a long way to get from one to the other right now. Every
event belongs to a bubble, so let's link them directly.
|
2025-01-17 14:40:36 +00:00 |
|
|
Kevin McConnell
|
415e872a2b
|
Combine concerns
|
2025-01-14 13:57:48 +00:00 |
|
|
Kevin McConnell
|
196575c0a2
|
Use a job to generate notifications
|
2025-01-13 14:21:47 +00:00 |
|
|
Kevin McConnell
|
a082eb75f5
|
Track events for new comments too
|
2025-01-13 14:21:47 +00:00 |
|
|
Jose Farias
|
f9712ea53f
|
Messageables don't belong to bubble directly
|
2024-10-27 11:57:33 -06:00 |
|
|
Jose Farias
|
a3edee6e58
|
Extract grouping of boosts
|
2024-10-25 16:06:34 -06:00 |
|
|
Jose Farias
|
7b104287ba
|
Roll up boosts server-side
|
2024-10-25 15:39:54 -06:00 |
|
|
Jose Farias
|
85d47a35ab
|
threadables -> messageables
|
2024-10-25 15:03:31 -06:00 |
|
|
Jose Farias
|
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 |
|
|
Jose Farias
|
ad88f90302
|
Fine not to denormalize user names in events
|
2024-10-24 15:50:00 -06:00 |
|
|
Jose Farias
|
c41da5837c
|
Add back bubble association to events
|
2024-10-24 11:22:23 -06:00 |
|
|
Jose Farias
|
567dec2197
|
Simplify threadable<>bubble relationships
|
2024-10-23 17:29:24 -06:00 |
|
|
Jose Farias
|
35a31e3203
|
Model threadables
|
2024-10-23 14:10:04 -06:00 |
|
|
Jose Farias
|
b0565fbf20
|
Spike workflows
|
2024-10-21 15:33:30 -06:00 |
|
|
David Heinemeier Hansson
|
1d404830f4
|
Must touch to bust bubble caches
|
2024-10-19 17:42:06 -07:00 |
|
|
Jose Farias
|
f4b5210ca1
|
Spike persisted filters
|
2024-10-16 16:41:11 -06:00 |
|
|
Jose Farias
|
ec7fc75054
|
Spike events system
|
2024-10-11 20:14:09 -05:00 |
|