csv-export plugin: custom data watcher #854
Merged
Conversation
This file contains hidden or 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
roblarsen
added a commit
that referenced
this pull request
Dec 3, 2013
csv-export plugin: custom data watcher
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
There are situations where the built-in watcher doesn't (or can't) notice when the data has changed. In addition, naively trying to watch for changed data can be inefficient compared with code that really knows when it has changed.
This change adds a new option, customDataWatcher. This is a function whose return value is appropriate to $watch in order to detect changes to the data; this allows apps using csv-export to specify the best way to detect changed data.