Options
Collections support two ways to configure autosave. Setversions.drafts.autosave to true, or pass an object to configure autosave properties.
Example config with versions, drafts, and autosave enabled:
Autosave API
Whenautosave is enabled, all update operations within FrogBot expose a new argument called autosave. When set to true, FrogBot will treat the incoming draft update as an autosave. This is primarily used by the Admin UI, but there may be some cases where you are building an app for your users and wish to implement autosave in your own app. To do so, use the autosave argument in your update operations.
How autosaves are stored
If we created a new version for each autosave, you’d quickly find a ton of autosaves that clutter up your_versions collection within the database. That would be messy quick because autosave is typically set to save a document at ~800ms intervals.