Am 28.09.2009 10:56, schrieb Christian Boos:
Felix Schwarz wrote:Hi, after playing around with IPermissionPolicy for some time I suspect that some use case are not really handled well by the current API and I would like to resolve that for 0.12 :-) 1. For every policy check I have to load the db object again even if the caller has a db object already. Can we make it resource_or_dbobject?Hm no, that will break the existing API.
That's why I proposed it for 0.12 :-)
2. Say I want to create a policy that prevents users to file tickets with a specific milestone (this needs triage). How to do that in a permission policy?I don't think a permission policy is adequate here, at least not in the current model where we don't check permissions on the milestone when creating a ticket. So maybe the ticket validation approach would be more adequate here (see ITicketManipulator).
The problem with ITicketManipulator is that it could be hard to hide the options for which the user does not have sufficient permissions already in the edit form...
fs
smime.p7s
Description: S/MIME Cryptographic Signature
