Skip to content
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

Jump to bottom

Add capability to choose which resources are included in the bundle based on include list #77

Closed
wdebeau1 opened this issue Jan 6, 2015 · 1 comment
Closed

Add capability to choose which resources are included in the bundle based on include list #77

wdebeau1 opened this issue Jan 6, 2015 · 1 comment
Labels
enhancement wontfix

Comments

@wdebeau1
Copy link
Collaborator

wdebeau1 commented Jan 6, 2015

http://jamesagnew.github.io/hapi-fhir/doc_resource_references.html describes how to control whether a referenced resource is included in a bundle (if you construct the ResourceReference by passing in a resource with its id set, it'll be included).
It would be nice if there was a way to control which of the ResourceReferences created this way were actually added to the bundle based on the list of Includes in the request. That way, Resources could be generated the same way regardless, and the bundling step could decide which resources to include and which to omit.
@jamesagnew jamesagnew mentioned this issue Jan 9, 2015
Closed
wdebeau1 pushed a commit to wdebeau1/hapi-fhir that referenced this issue Mar 4, 2015
hapifhir#77 bundle factories now do resource inclusion based on a Bun…
7295501 
…dleInclusionRule (either by the resource being fully populated - the old way or based on the include parameter - the new way). Can be configured by RestfulServer.setBundleInclusionRule. Old tests set to use the old behavior, at least for now.
wdebeau1 pushed a commit to wdebeau1/hapi-fhir that referenced this issue Mar 4, 2015
hapifhir#77 bundle factories now do resource inclusion based on a Bun…
08aa2ed 
…dleInclusionRule (either by the resource being fully populated - the old way or based on the include parameter - the new way). Can be configured by RestfulServer.setBundleInclusionRule. Old tests set to use the old behavior, at least for now.
wdebeau1 pushed a commit to wdebeau1/hapi-fhir that referenced this issue Mar 5, 2015
hapifhir#77 bundle factories now do resource inclusion based on a Bun…
b38bce8 
…dleInclusionRule (either by the resource being fully populated - the old way or based on the include parameter - the new way). Can be configured by RestfulServer.setBundleInclusionRule. Old tests set to use the old behavior, at least for now.
wdebeau1 pushed a commit to wdebeau1/hapi-fhir that referenced this issue Mar 5, 2015
hapifhir#77 bundle factories now do resource inclusion based on a Bun…
965a5d4 
…dleInclusionRule (either by the resource being fully populated - the old way or based on the include parameter - the new way). Can be configured by RestfulServer.setBundleInclusionRule. Old tests set to use the old behavior, at least for now.
wdebeau1 pushed a commit that referenced this issue Mar 12, 2015
#77 - Fixed wildcard string compare that was breaking inclusion
bac290b
@stale
Copy link

stale bot commented Mar 20, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Mar 20, 2020
@stale stale bot closed this as completed Mar 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement wontfix
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@wdebeau1