Permissions
Group userAbilities by user type — default, trial, expired, full membership, and so on.
Permissions
Tests first, group by feature, one source per permission — same behavior, organized luggage.
- 01
Tests are the map
- From 19% path coverage to every path
- Understand behavior before changing anything
- Safety net for every future change
- 02
Group by feature
- One handler per feature for defaults
- Defaults are findable, even by non-engineers
- Same logic — different organization
- 03
One source per permission
- Duplicates collapsed into a single handler
- Change once, applies everywhere
- No more hunting through ~800 lines
- 04
The payoff is real
- Premium channels: knew where to add it
- And later — knew exactly where to fix it
- Worth doing regardless of where permissions live
Same content, organized luggage — a finite, named structure instead of a pile to dig through.