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

Validate theSearchParamRegistry is not null #2142

Merged

Conversation

blangley28
Copy link
Contributor

in the R4 ConformanceProvider there are validations on theRestfulServer, theSystemDao, and theDaoConfig to be not null but no such validation for theSearchParamRegistry.

However, if you look at line 128 it assumes mySearchParamRegistry is not null. Passing in a null value will cause a null pointer exception. Since these validations already exist it is easy enough to just add a check for the search param registry too.

The DSTU2/3 Conformance Providers do not include this argument and the R5 version doesn't validate any of the arguments so I only added the check here.

Copy link
Collaborator

@jamesagnew jamesagnew left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution! Merging now.

@jamesagnew jamesagnew merged commit d468183 into hapifhir:master Oct 23, 2020
jamesagnew added a commit that referenced this pull request Oct 23, 2020
HananAwwad pushed a commit to HananAwwad/hapi-fhir that referenced this pull request Jan 6, 2021
HananAwwad pushed a commit to HananAwwad/hapi-fhir that referenced this pull request Jan 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants