You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Olabusayo Kilo (Jira)" <ji...@apache.org> on 2023/09/11 15:09:00 UTC

[jira] [Updated] (DAFFODIL-2842) Length facet doesn't behave like minlength==maxlength when validation is limited

     [ https://issues.apache.org/jira/browse/DAFFODIL-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olabusayo Kilo updated DAFFODIL-2842:
-------------------------------------
    Summary: Length facet doesn't behave like minlength==maxlength when validation is limited  (was: XSD Length doesn't behave like minlength==maxlength when validation is limited)

> Length facet doesn't behave like minlength==maxlength when validation is limited
> --------------------------------------------------------------------------------
>
>                 Key: DAFFODIL-2842
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2842
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Back End
>    Affects Versions: 3.5.0
>            Reporter: Olabusayo Kilo
>            Priority: Major
>
> When validation is limited, the length facet isn't enforced during validation and it requires the use of maxlength and minlength facets for enforcement.
> Possible solution: Inside daffodil really there should be use of maxLength and minLength values in the DSOM model, but those should be populated regardless of whether maxLength and minLength are specified separately, or only length is specified.
> It should also test to ensure you don't specify both length and either of maxLength/minLength as distinct values.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)