So I have a plug, in a pipeline attached to a scope, which checks authorization for the routes in that scope. But now, there’s 1 dang route which suddenly has to require an additional permission. Thoughts?
I’d kind of like:
scope "/foo", Bar do pipe_through[...] get ... get ... with_added_pipeline ... do post ... end end
But I doubt that’s actually supported. I’m leaning toward a plug that actually looks at the path, and checks the additional permission, or not, based on the path. But that gets the requirement kind of far from the route, and is why I didn’t like it so much.