We all have seen we need a persistent object to upload a file. Sometimes you do not want the file to be persisted. An example is an anonymous upload with maybe sensitive data. It would be great to set an option to use client-side base64 encryption and send the string representation instead of the file.
The developer needs to decrypt the string-to-file again but that can be done in a controlled (secured) setting.
For now I use some javascript to get this done but implementing this in the fileupload widget would be great (and secure ;))
Yes, agreed all the 'heavy-lifting' should be integrated in the widget so a developer has the same kind of experience and should indeed not be bothered with the encoding en decoding.
Building clean and safe file uploads can indeed be a thing in Mendix. The automatic commit when uploading a file is sometimes unwanted and the auto-commit side effects you sometimes get are definitely a problem.
I would still like to use the functionality in the same way we're used to, just with a non-persistent FileDocument. Stick to the low-code approach - as a Mendix developer I shoudn't have to care if there's a base64 encoding, or if the file is stored in a /tmp folder.