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.
New issue
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
feat(#9193): add functionality of getting places as pages or async iterables in cht-datasource #9368
feat(#9193): add functionality of getting places as pages or async iterables in cht-datasource #9368
Changes from 5 commits
c103b2b
1e3a75e
875b634
4851522
dd89f68
71fbe58
7f2bddf
c1f6b1d
74b34b2
9b50b5d
3be9efe
b47b5be
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks to the wonders of generic types, we can do something like this:
And then we do not have to have the
as Page<Place.v1.Place>
assertions in the person/place code! The only other required change is that we update thefilter
call below to be explicit about the assertion:const newDocs = docs.filter((doc): doc is T => filterFunction(settings, doc, doc?._id));
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Although this would eliminate the use of unknown in the function, I couldn't get this to work without the
as Page<Place.v1.Place>
assertions because<T extends Doc>
would mean they have properties fromDoc
butPlace
andPerson
have additional properties for which errors are thrown in other parts of the code.