chore: remove dead sinceToken code #6163
Merged
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
|
Can you double check the docs please, so we can make sure they are up to date |
igorT
approved these changes
Jun 17, 2019
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.
Since an unknown time many many (many) years ago,
findAllhas not supported use of asinceToken, even though the adapter API still has a slot for it in the arguments passed toAdapter.findAll.This PR removes a bit of infra that attempted to pull an always missing sinceToken from an always empty cache attached to the InternalModel cache where we were never stashing one to begin with.
If this is a feature we wish to support, we should design a mechanism through which consuming applications can retrieve and update the sinceToken.