We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Right now this API is in my mind. SyncedDB has a nice and simple syntax to express IDBKeyRange so we can expand it for skip and offset (and filter either in the future, probably).
houses.byStreet.query({ gt: 'Somewhere 2', lte: 'Somewhere 4', skip: 20, // <- New API limit: 10 // <- New API })
sdbIndex.inRange
.query()
The text was updated successfully, but these errors were encountered:
@paldepind I think this topic will interest you as you mentioned in the list.
Sorry, something went wrong.
I changed my mind, using inRange as a method name just makes sense
inRange
I force-removed the merged commit and rebased these commits 2586220 b28e0da 2bb9d8f 18d2c30
Successfully merging a pull request may close this issue.
Right now this API is in my mind. SyncedDB has a nice and simple syntax to express IDBKeyRange so we can expand it for skip and offset (and filter either in the future, probably).
sdbIndex.inRange
can be deprecated in the case.query()
will be keeping users away from touching IDBCursor directlyThe text was updated successfully, but these errors were encountered: