hasPermission

Hi jlutterloh,

I'm sorry it took so long for someone to respond to this, but this is a great post and I wanted to make sure that provided some input, even if it is a month later.

The coreNode.permissions.hasPermission object was an experimental object that was added for a single use-case.  We actually have a set of interal policy checks in the core Lithium application that combine permission checks, admin settings checks, back-end configuration checks, and other policies but we don't have a way yet to expose these to customizations.  Since most of our polices are quite complex, and include more than just permission checks (also settings, back-end configs, and other checks), a simple permission check may not be the best or most accurate way to determine if a user can take a certain action.

It would be very helpful to understand what you are/were trying to accomplish.  Perhaps I can suggest a good way to accomplish what you want to do using the customization tools you have (although since it's been a month, perhaps you already accomplished it; if so, it would be good to hear about what you did).  At the very least, it will be helpful for the developers and product managers that work on our customization frameworks (REST, Freemarker, etc.) to hear more use cases that can help shape what customization points we build out.

Thanks!

-Doug