Closed SirSeim closed 1 year ago
On the form view implementation, we'll need to dynamically add fields for setting things, this might help:
To go from Rename to Summary, this answer may help. We can use a button to call on code to construct the renamings and then push the summary view with the compiled information.
The other main option could be to have more complex stateful Files array that get acted on directly in the rename form that can then be passed directly to the summary view. The issue there would be handling manual renames on the summary screen that are properly propagated back to the rename view if that is done.
Once an Addition has completed downloading, be able to initiate a flow to complete it's addition to the library.
Steps to complete:
It is assumed this will be a multi-view flow for the user. Until the final confirm button is hit, the user should always be able to go backwards in the flow to correct any mistakes. For now, images and other files should be ignored. They will not end up in the final rename.
Once the UX has been established, then the Bakus Service endpoint can be defined to carry out the process.