-
Notifications
You must be signed in to change notification settings - Fork 166
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
Engine: Better resolve handling for search parameters of type 'reference' #571
Engine: Better resolve handling for search parameters of type 'reference' #571
Conversation
babf342
to
e5f079b
Compare
e5f079b
to
41f4b11
Compare
I think it is better to put the |
I agree, I did it for the time being to not force a major version bump since we then are breaking binary compatibility by changing the IFhirModel interface. But maybe it's time for that anyways. |
Oh,I see. |
62d35b5
to
503b619
Compare
This enhances our resolve handling for reference types profoundly. This adds ResourceResolver and makes use of FhirEvalutionContext.ElementResolver to wire up ResourceResolver.Resolve() in IndexService. Co-authored-by: haowang <593301179@qq.com>
d1a4cd2
to
c31c1ba
Compare
Co-authored-by: haowang <593301179@qq.com>
New backup image after better resolve handling for reference types in IndexService.
c31c1ba
to
614f8f3
Compare
For this to take effect on existing implementations it is necessary to rebuild the index by using the Admin UI that comes with Spark.Web or wire up
IndexRebuildService
in your implementaion.Se independent commits for details.
Resolves #436
Resolves #521
Resolves #522
Resolves #526
Co-authored-by: @whyfate