er314

Hi, Actually, as hinted by @iamkeir here https://github.com/cferdinandi/bouncer/issues/39#issuecomment-519156159 , the ability to configure custom error message per [ field + constraint-type ] (instead of only per [ constraint-type ] )...

Hi, Actually, the ability to configure custom error message per [ field + constraint-type ] (instead of only per [ constraint-type ] ) **IS readily supported** by the current featureset....

Hi, thanks for sharing your experiments, I agree that this approach (= event driven changes to the inclusivity setting) seems fully valid. On my side, now I've got a solution...

This would really be awesome (to me :-) : strict access control to file assets exactly where needed, and no performance impact elsewhere. An opinion about the feasibility ?

Any feedback on this ? This would be awesome, and this would bring comprehensiveness & consistency in terms of access control : fine-grained down to field-level, whatever the access control...

up ! an aknowledgement of reading, in the form of a polite "no, it's not in the roadmap", would be greatly appreciated ! 😁 so I can move forward to...

For the record (as I myself had forgotten), here is Ryan's answer, done on PW forums in sept. 2022, regarding this feature request : > Yes, I think that's a...