A --unsafe
/ --lossy
type flag for working with corrupted files
#246
Labels
enhancement
New feature or request
external
Issue depends on external factors
roblox
Issues pertaining to the built-in Roblox library
Thank y'all again for resolving the recent Roblox introduced serialization issue yesterday, however I do think it illuminated a need for working the datamodels in a way that doesn't always assume validity.
This is something other roblox file modifying tools like rbxmk can do - in fact yesterday I wrote this code to get around the issue:
I would have much preferred to write this code in Lune - I really like Lune. However it would refuse to open / let me edit any part of the corrupted place file. I think that there should be support for some proactive patching / cleaning of corrupted files. For example if a single property is causing an error, just reset that property to the default / remove it entirely. Obviously you'd want to print a warning whenever it does this, and I think it would be best for this behavior to be opt-in via flag. But I think there is a legitimate need for it.
The next time a file is corrupted, it might not be some global outage that immediately gets fixed - it might be due to developer error, I don't know about y'all but I've certainly made mistakes editing a DOM before. I think Lune would be a better tool if it allowed developers to not be blocked when that happens.
Anyways, thank you for your time!
The text was updated successfully, but these errors were encountered: