Use 'live' instead of 'continuous' keyword #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Great project, by the way! |
bean5
force-pushed
the
continuous-to-live
branch
2 times, most recently
from
5b54696 to
95d687d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I think 'live' is the correct way to sync continuously. Was
continuousperhaps used in an older version of pouchDB?On second look, it appears that you are using pouchdb.nightly from 2013-07. The newer version does support
continuous. In fact, it supersedes any usage oflive.Not sure what you'll want to do, but might as well start a conversation. PouchDB documentation says to use
liveto sync continuously, but technically they both work with the newer version.