mirror of
https://github.com/mauriceboe/TREK.git
synced 2026-10-18 21:16:47 +00:00
d1a13058a6
@RequireAddon has sat on the controller since the domain was written and did nothing: it is metadata, AddonGuard was not in the chain, and it is not one of the three global guards either. The addon ships disabled (seeds sets enabled 0), so on any instance that never switched it on, all six via routes answered anyway. Two doc comments in this repo already describe the behaviour this commit creates rather than the one it replaces. AddonGuard leads the chain, the way reservation-import and collections do it, because a disabled addon owes an anonymous caller a 404 rather than a 401.