[
https://issues.apache.org/jira/browse/DAFFODIL-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Thompson closed DAFFODIL-2842.
-----------------------------------
Verified the specified commit (commit 3e936cfec9c1f2897be2b619a4c586a13b4304c5)
is included in the latest pull from the daffodil repository.
Verified, via review, changes identified in the commit comment were
implemented.
Verified the affected daffodil subproject sbt test suites executed
successfully, including the modified and added tests.
Verified the nightly test suite executes successfully with no unexpected
failures.
> 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
> Assignee: Olabusayo Kilo
> Priority: Major
> Fix For: 3.7.0
>
>
> 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)
