This provides a way to set the level of involvement that a user has with
a collection, and from which we determine the level of notifications to
send. Users can be access-only, watching, or being notified about
everything.
If you're access-only, you won't get an notifications. If you're
watching, you'll only get notifications for the items you're watching
(which includes the items you've been assigned, have commented on, etc).
If you're set to everything you'll get notifications about all activity
in that collection.
This change replaces our previous concept of subscriptions. Where
previously you'd subscribe to a collection to get notifications in it,
now you'll simply set the notification level on your access.
The previous implementation would delete all accesses if the bucket
was not all_access.
I think it's simpler to move the bucket workflow into a separate
Buckets::WorkflowsController, rather than deal with different sets of
params from different forms in the existing BucketsController.
- Rearrange the _tags and _tag partial, so they are properly nested concerns
- Add turbo frames for _tags and _tag
- Load _tag in a separate request, so it's not cached with the card
- Cache _tag using the bubble and the account
- New model behavior: touch Account when tags are added or removed
- New controller action: "new" for taggings toggles, which renders the _tag partial
- Updating taggings responds with a turbo stream response that updates the _tags frame
This is very much a parallel change to what was done with assignments
in #317.
We use a true/false preference so we can tell the difference between
disabling the watch vs never having the watch. This is so we can toggle
off and on the preferences for a container (like the bucket) without
losing any bubble-specific preferences.
This test would fail when the two timezones is covers landed on
different days (like in the first few hours of UTC). So let's fix the
test to a particular moment in time.
Previously when an item was `created`, we'd track the event, update the
summary text, and broadcast the notifications. But now that we have a
draft state, we shold do all of this when it's published instead.
* main: (23 commits)
Improve the flow for editing bubble titles
Use path helpers in tests
Revising access shouldn't do a replace turbo-action
Split into new tests
Update this test, too
Adjust tests to match new behavior
Reapply "Destroy equivalent filters upon resource removal"
Revert "Destroy equivalent filters upon resource removal"
Destroy equivalent filters upon resource removal
Don't autocomplete
Rework boosts form so you can enter any integer
Pull out access_menu_tag
Punt on removing filters for inaccessible buckets
Can't see bubbles in buckets you've lost access to
Users can remove themselves from buckets
Fix redirect assertion
Fix redirect assertion
Submit form when toggling all-access + caching
Unnecessary parens
Can't revoke access to all-access bucket
...
Jorge Manrubia