Differentiate between regular autosave delay and submit autosave delay #139
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Differentiate between :
options.autosave.delay
options.autosave.submit_delay
I'm working for a project (https://github.com/zestedesavoir/zds-site) where we put the
options.autosave.delay
at 1 second because we want to save the content each 1 second. But since the submit request takes more than 1 second EasyMDE thinks the submit as failed so it saves the content in thelocalStorage
.I didn't find a better name than
autosave.submit_delay
, any suggestion is welcome.This might be considered as a breaking change. If it is the case, we could maybe use
easyMDE.options.autosave.submit_delay || easyMDE.options.autosave.delay || 10000
?