On Jan 19, 1:17 pm, Andy C <[email protected]> wrote:
> Is the UI for ACL fully functional or are to referring to the
> functions under the hood that mere mortals (end user) can't see ?
No. The UI for ACL is very broken. The underlying functions that it
uses fail to capture the full access granted to a user for a specific
token. For example, if you have read+write access to a token, the UI
will only show that you have read access.
All of the ACL-related classes need massaged, actually. Names of
functions and variables need to be more clear about what they're
doing. In most cases, "permission" shouldn't be used in a function
name or variable. A "token" is a thing to which you can be granted
"access". Keeping naming uniform will help readability of the class,
which most people already approach as being complicated.
Owen
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/habari-dev
-~----------~----~----~----~------~----~------~--~---
