Rename movies

[SirSeim]

Once an Addition has completed downloading, be able to initiate a flow to complete it's addition to the library.

Steps to complete:

1. First action is to decide that this Addition is a movie. Other types will get their own flows appropriate to them.
2. For movies, establishing the title and year are core to the rename, that should be established first. Plex has recommendations on how this should work.
3. Categorize the subtitle files properly. For each subtitle, a language needs to be associated to it. Use ISO 639-1 codes. Plex has recommendations on how this should work.
4. Handle any remaining video files as extras. Plex has recommendations on how this should work.
5. See a summary of the full list of file renaming that will occur, along with the confirm button that will carry out the changes.

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.

[SirSeim]

On the form view implementation, we'll need to dynamically add fields for setting things, this might help:

• handling array of bindings
• another idea for handling bindings
• Review new SwiftUI additions in WWDC 2022: video

[SirSeim]

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.