StoreAdapter: Add test and proposed fix for totalLength promise #98
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
|
Merged |
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 noticed another
totalLength-related API issue after removing what should be considered unnecessarywhencalls from dgrid. It appears thatStoreAdapterdoes not ensure thattotalLengthis a promise on adapted stores.I've pushed a commit that adds a test for this, and proposes a fix. I'm not sure whether this is really the right fix - I'm wondering whether it'd make sense to normalize this in
QueryResultsitself, instead.I'd also ask that this be ported to the 1.0 branch for a 1.0.2, along with #97 when it's fixed. dgrid 0.4.1 would benefit from these. Thanks.