Community
Participate
Working Groups
Build Identifier: Given the following attribute definitions and the current implementation <AD default="password" id="password1" min="3" type="Password"/> <AD default="password" id="password2" max="8" type="Password"/> <AD default="password" id="password3" max="8" min="3" type="Password"/> A value of "12" is valid for password1. A value of "123456789" is valid for password2. Both are invalid for password3. The implementation ignores max or min when specified independently. This only happens for the String and Password attribute types. I can find no justification for this. Seems to me min or max should always be honored. Reproducible: Always
Created attachment 183049 [details] Proposed Patch 1 Splits min and max into two separate checks instead of one. Note this patch has some residue from Bug 327173. I'll repatch once that is released if needed.
Created attachment 183051 [details] Test Patch 1 Adds some MetaType tests to compendium.tests related to this bug.
(In reply to comment #1) > Created an attachment (id=183049) [details] > Proposed Patch 1 > > Splits min and max into two separate checks instead of one. Note this patch has > some residue from Bug 327173. I'll repatch once that is released if needed. I released the fix in bug327173. Please provide an updated patch. Thanks.
Created attachment 183171 [details] Proposed Patch 2 Repatched from latest HEAD contents.
Thanks John. I released the latest patch.
I released the test patch also.