resources for groups

[fruitloop]

Hi,

I'm using Slim v3 and I want to secure a single group with ACL.
I have a "problem".

When I secure a group like this:

$app->group('/extremelyLongStringThatIsNotFunToType', function() {
  $this->get('/short', function($req, $res, $args) {...});
  $this->get('/and', function($req, $res, $args) {...});
  $this->get('/readable', function($req, $res, $args) {...});
})->add(new \Geggleto\Acl\AclRepository([$_SESSION["role"]], [
  "resources" => ["/extremelyLongStringThatIsNotFunToType/short", "/extremelyLongStringThatIsNotFunToType/and", "/extremelyLongStringThatIsNotFunToType/readable"],
  "roles" => ["admin", "user"],
  "assignments" => [
    "allow" => [
      "admin" => ["/extremelyLongStringThatIsNotFunToType/short", "/extremelyLongStringThatIsNotFunToType/and", "/extremelyLongStringThatIsNotFunToType/easy"],
      "user" => ["/extremelyLongStringThatIsNotFunToType/short"]
    "deny" => []
  ]
]));

the resources get rather long, is there a way to use a shorter form (like only the path inside the group and not the whole group/path string?)

[geggleto]

Hey, I will have to look into some solutions.

For now I would recommend putting the resource string into the container to save some typing. In theory I think I might be able to merge all of the "allow" assignments to construct resources and roles ?

[fruitloop]

Hi,

you mean something like this?

$long = 'extremelyLongStringThatIsNotFunToType';
"resources" => ["$long/short", "$long/and", "$long/readable"]

Yesterday I was wondering if we could use the names $app->get(...)->setName('foo'); to define the routes. That would work for me since I am naming about every route to use in my TWIG templates.

[geggleto]

Hmm that's an interesting thought. If we wanted to use the app hooks we would need to wrap the Slim App to intercept those method calls.

[lotharthesavior]

AOP coming to the scene