Nate Abele

What would be the use case for this?

Got it, thanks for the feedback, guys.

Code: ``` php public $hasMany = array( 'Comment'=>array( 'key'=>array('id'=>'post_id'), 'order'=>array('created'=>'DESC') ), 'Favourite'=>array( 'key'=>array('id'=>'post_id'), 'order'=>array('created'=>'DESC') ), 'Like'=>array( 'key'=>array('id'=>'post_id'), 'order'=>array('created'=>'DESC') ), 'Dislike'=>array( 'key'=>array('id'=>'post_id'), 'order'=>array('created'=>'DESC') ), 'CommentCount'=>array( 'key'=>array('id'=>'post_id'), 'order'=>array('created'=>'DESC'), 'fields'=>array('count(Comment.id) as "count"'), 'source'=>'comment',...

If there's a simple work-around for this that doesn't add any overhead, that's fine. Strictly speaking, though, this is not a bug. The `static` keyword is only intended to be...

Hey @jails! I'm finally recovering from having a kid, and getting sleep again, so I had a chance to look at this. One thing that would help here is to...

@jails In that plugin, would the admin rule be "scoped" to only apply to that plugin?

It's kind of a separate thing.

I've been meaning to change the API to eliminate the ambiguity. What do you think: `Session::("configName.keyName.subKeyName", ...)` or `Session::("configName", "keyName.subKeyName", ...)`?

I believe it will, actually, which is why I brought it up. ;-)

@mariuswilms I don't recall, is this on the critical path for the request/response loop? If so, it should probably be benchmarked for performance impact.