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

Daniel Keir Haywood updated CAUSEWAY-4026:
------------------------------------------
    Summary: Add ReplayableCommand#isExportable so can easily see if there's a 
command outside of the dotted path.  Also, support property edits  (was: Add 
ReplayableCommand#isExportable so can easily see if there's a command outside 
of the dotted path.)

> Add ReplayableCommand#isExportable so can easily see if there's a command 
> outside of the dotted path.  Also, support property edits
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAUSEWAY-4026
>                 URL: https://issues.apache.org/jira/browse/CAUSEWAY-4026
>             Project: Causeway
>          Issue Type: New Feature
>    Affects Versions: v2 maintenance-branch
>            Reporter: Daniel Keir Haywood
>            Assignee: Daniel Keir Haywood
>            Priority: Major
>             Fix For: 4.0.0-M2, v2 maintenance-branch
>
>
> Command export validation currently runs only after the user attempts an 
> export, so users must discover sequence problems through a failed action.
> Showing each replayable command's exportability in the export manager list 
> gives earlier feedback and helps users reorder or include prerequisite 
> commands before exporting.
>  
> ~~~
>  
> `CommandExportManager_exportSelected` validates selected commands only when 
> the user invokes the export action or when selected action parameters are 
> validated.
> That validation checks that command targets and reference parameters are 
> export roots or results from earlier commands in the baseline-bounded export 
> sequence.
> The export manager already exposes a unified `commands` collection of 
> `ReplayableCommand` view models, but each row does not tell the user whether 
> it will pass export validation at its current position.
> The requested implementation uses `Scratchpad` as a request-scoped handoff 
> from `CommandExportManager#getCommands()` to the `ReplayableCommand` 
> instances constructed while rendering the collection.
> This keeps the replayable command memento unchanged and allows commands 
> created outside this export-manager interaction to report an unknown 
> exportability value.



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

Reply via email to