RFC: Make `access` the action verb for authorization about authorization HOT 7 CLOSED

The concept of apply scope make sense. I'm not sure if we can make scope, action, operation consistent in all places.

I'm dropping the action name change.

from authorization.

I should point out that I'm suggesting a config format change to combine the various action-specific configs into a single action => [config] format. This will avoid the need for confusing functions.

from authorization.

👍 for AuthorizationComponent::authorize() => AuthorizationComponent::access(), not sure about replacing the other methods with setConfig(). I haven't used the component enough to have an informed opinion on it.

from authorization.

👍 for AuthorizationComponent::authorize() => AuthorizationComponent::access(), not sure about replacing the other methods with setConfig(). I haven't used the component enough to have an informed opinion on it.

The reason for the change is authorizeModel() doesn't make sense especially now. I could replace it with another name, but seemed awkward.

It's an alternative for discussion.

from authorization.

We already use the term scope in Authorization to mean the type of access requested for a resource. It make sense to use it consistently.

Using scope to mean two different things in this plugin is a bit concerning to me. Could access() use operation instead?

from authorization.

Using scope to mean two different things in this plugin is a bit concerning to me. Could access() use operation instead?

I also want a consistent word for the "type of access" being requested for anything. It's currently "action", and I think that's confusing. I was going to suggest scope since we have applyScope ... but maybe that name needs to be adjusted as well since apply doesn't make sense.

from authorization.

The idea behind apply was that those methods mutate a query or selection so that access controls have been 'applied'.

from authorization.