My thoughts, while still forming, are:
1) Yes, that's how I pictured it, though there might be some syntax options that could make that more palatable.
2) $routes array is probably bettern named $uri - since it would be the input url. This makes it simple to modify the underlying guts of the site, while still keeping things intact, as long as the URI structure doesn't change.
3) I had that thought, also, and haven't explored it much yet, but it seemed easier to keep a mental picture of what was affecting a portion of the site by grouping them by uri. Instead of checking 3 or 4 arrays to make sure that the admin area had everything applied to it, etc. I guess using your example, it would be something like this, then:
Code:
public $filters = [
'isLoggedIn' => ['admin/*', 'profiles/*', 'users/*', 'posts/*/store', 'posts/*/destroy'],
'somethignElse' => ['admin/*', 'profiles/*', 'users/*', 'posts/*/store', 'posts/*/destroy'],
];
In some ways this is definitely cleaner, but I can't help but think that once a site gets big enough, it's going to be confusing to keep in mind what's being protected either way. The first way (with some additional syntax for grouping routes, or something) makes it easier to look at a portion of your site and make sure it has all of the filters applied it needs, to me anyway.
I'll have to make a list of general types of filters that we'd expect to be used and see which way would be easiest for each of them to be applied.
