enapps-enorman commented on pull request #471: URL: https://github.com/apache/jackrabbit-oak/pull/471#issuecomment-1036601054
> which apparently only stores properties directly below the user node. This is not true, we do use properties stored under subnodes as well. We use a custom primary type and acls to control the read/write access to the subnodes. None of the subnode handling code required the changes proposed here as that part already worked ok. Anyways, I have committed the additional tests to demonstrate what we are doing at [4b18b72](https://github.com/apache/jackrabbit-oak/pull/471/commits/4b18b728f1470bc403484c8b9c4965e94120a05b) for you to review and consider. Can we please evaluate this PR on the narrow goal of making the (non subnode) authorizable properties that are defined by a configured mixin readable as authorizable properties? All the other topics you keep bringing up seem to be out of scope and I would hope that those could be discussed and considered separately. Trying to get this PR accepted has been frustrating and I've already spent more time on this than I wanted to, so I would appreciate an answer as to whether the PR will be merged or not. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
