[
https://issues.apache.org/jira/browse/CAUSEWAY-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andi Huber updated CAUSEWAY-3436:
---------------------------------
Fix Version/s: 2.1.0
(was: 2.0.0)
> [demo app] @Parameter#maxLength seems to be evaluated at the action level
> rather than param level.
> --------------------------------------------------------------------------------------------------
>
> Key: CAUSEWAY-3436
> URL: https://issues.apache.org/jira/browse/CAUSEWAY-3436
> Project: Causeway
> Issue Type: Improvement
> Components: Core, Viewer Wicket
> Affects Versions: 2.0.0-RC1
> Reporter: Daniel Keir Haywood
> Priority: Minor
> Fix For: 2.1.0
>
> Attachments: image-2023-04-20-06-53-59-278.png,
> image-2023-04-20-07-12-37-411.png, image-2023-04-20-07-23-39-210.png,
> image-2023-04-22-06-53-49-992.png
>
>
> In demo app, on the @Property#maxLength page, also demonstrates use of
> @Parameter#maxLength.
> When specifying a string that's too long, the validation message appears in
> the same place that a validateXxx() message would appear (ie for the entire
> action prompt), rather than scoped to the param (as it would for a
> validate0Xxx() message).
>
> !image-2023-04-20-06-53-59-278.png|width=729,height=174!
>
> similarly for @Parameter#mustSatisfy:
>
> !image-2023-04-20-07-12-37-411.png|width=736,height=209!
>
> similarly for regex:
>
> !image-2023-04-22-06-53-49-992.png|width=756,height=177!
> by way of comparison, @Parameter#optionality=MANDATORY is rendered in correct
> place:
>
> !image-2023-04-20-07-23-39-210.png|width=949,height=200!
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
