Update to allow for new entry not to be added to the data source #274
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
New setting 'confirm.resolve.skipAdd'=true will skip adding the new entry to the data source. Added to allow for better integration with rxjs and ngrx.
|
duplicate of #280 |
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.
Change:
New setting 'confirm.resolve.skipAdd'=true will skip adding the new entry to the data source. Added to allow for better integration with rxjs and ngrx.
Short summary of issue:
The function event.confirm.resolve() does two separate things at the moment:
This pull request allows the event.confirm.resolve() to only (1) modify the UI controls, and not (2) add the new entry to the data source by setting the new parameter 'skipAdd' to true.
The problem this new feature solves is further described in Issue #273.