wikiausers / fandom-image-transfer Goto Github PK

The app is not translatable and should be made so at some point.

From one of the testers:

Large files seem to error out with status code 503 when trying to upload them. While this is a server error, it is entirely possible that the program hasn't properly downloaded the file it is trying to upload.

With all the upcoming wiki merges with Gamepedia, it might be a good idea to add support for Gamepedia wikis here too.

Most of the code is located in app.js at the moment. Consider splitting away separate components and using Redux for managing state.

From one of the testers:

If this cannot be reproduced by normal means, it would still be useful to keep the log list always on the bottom.

We would need one before a public release, but it would have to be created from a macOS computer (Apple's policies).

Currently, the URL fields don't make it obvious that community isn't a valid value. There should be more variants of URLs allowed, and possibly a system to check on which domain is the wiki located automatically before starting the process.

See also #4.

Since the program is already mass-downloading images, it could be made possible that these images aren't uploaded if configured so.

Currently, the program stops the upload process completely whenever it encounters an error. Ideally, errors in the response status codes should be handled by retrying the upload and errors elsewhere should be logged in the user interface and the files that errored should be stored somewhere so the user can retry uploads for those.

Files such as Community-header-background and Wiki-background cannot be uploaded outside of ThemeDesigner. Current behavior is attempting to upload them and succeed by uploading them with an extension (which is not what the user wants). Better behavior would be to not upload the image and warn the user to upload the image through ThemeDesigner. Ideal behavior would be to upload the image through ThemeDesigner if the current user has permissions for it, or warn and ignore if they do not.

As it currently is, the app will log warnings that occur during uploading as JSON. Find a way to handle all possible warning and error scenarios so proper messages could be displayed in the logs.

Currently, the program defaults to setting the same page content as the summary if page content isn't specified. Consider doing either:

• Removing that fallback - introduces inconsistencies between the special pages and the program
• Introducing a checkbox for separating summary from content - introduces more interface complexity.