Since the system does not currently provide version history or an undo option, any changes made to data models or views are irreversible. This poses a serious usability problem, particularly when users alter collections inadvertently or structurally. Errors necessitate manual rollback or full reconstruction of impacted schemas, which can be laborious and prone to errors, in the absence of a mechanism to undo or monitor changes. A simple change history log or a temporary undo option following updates or deletions would significantly increase flexibility, lessen user annoyance, and boost data integrity in general.
There are no related plans at the moment.