Allow attributes matching a particular pattern alone works as expected.
Disallow attributes matching pattern "google" not working as expected and discards http://yahoo.com
If I am not wrong disallowAttribute() does a allowAttribute() matching a _REJECTALL policy so no further matching can be called on the returned AttributeBuilder. Is my understanding correct? I understand the library is whitelist based and everything not allowed by default is rejected by default. But, in our case we ship a minimal policy and the consumer may still want to restrict few more entities. If my understanding above on why this doesn't work is right, is there a way to achieve it?
I am trying to disallow attributes matching a specific pattern.
Allow attributes matching a particular pattern alone works as expected. Disallow attributes matching pattern "google" not working as expected and discards http://yahoo.com
If I am not wrong disallowAttribute() does a allowAttribute() matching a _REJECTALL policy so no further matching can be called on the returned AttributeBuilder. Is my understanding correct? I understand the library is whitelist based and everything not allowed by default is rejected by default. But, in our case we ship a minimal policy and the consumer may still want to restrict few more entities. If my understanding above on why this doesn't work is right, is there a way to achieve it?