-
Notifications
You must be signed in to change notification settings - Fork 213
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
Iterable support in FHIRSearch #172
Comments
@LanaNYC I may have a little time this week/next to look at this - just pinging because I didn't want to overlap efforts, in case you had started looking at this (you had mentioned maybe having time to look at this too, in your original pagination PR) |
@mikix Hey, sorry for the delay — I started looking into it but got interrupted. I was planning to get back to it next week, but I don't want to hold you up. Let me know if you'd prefer to take it over. |
@LanaNYC ah cool no - no worries about a delay, there's no schedule here. I was just reminded of this and was curious where your brain was at. If you're planning to look at this, go for it, and I'll happily review. If it does end up sliding off your plate, let me know and I can pick it back up. |
Solved by #174 - will be in next release! |
As discussed in #169, we would like to create a parallel set of functions inside of FHIRSearch that behave more like modern python iterables, shadowing existing functions for now in order to prevent breaking the API. The discussed approach is as follows:
The text was updated successfully, but these errors were encountered: