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

#171: improve documentation in properties files #177

Merged
merged 8 commits into from
Feb 20, 2024
Merged

Conversation

mattStorer
Copy link
Collaborator

added all sorts of documentation to properties files.

changes include:

  • removed unused properties Observation.Category.Query and Observation.Category.Strategy from fhirqueries.properties
  • renamed Observation.Code.Query to Observation.Query, and renamed Observation.Code.Strategy to Observation.Strategy in fhirqueries.properties, as there is now only one version of the Observation query that exists (the other Category form was literally never used, so I removed it as a part of this documentation task, I want to make sure that we're not documenting things that are never used anywhere ever)
  • renamed service-request-order.bp-goal.custom-codings to service-request-order.bp-goal.codings in fhirconfig.properties

…oal.custom-codings to service-request-order.bp-goal.codings (removed "custom-"), because the "custom-" part is a convention that indicates that there is a hard-coded coding that will always be used, and these "custom" codings are supplemental. that is not the case here.
…st-order.bp-goal.codings (removed "custom-"), because the "custom-" part is a convention that indicates that there is a hard-coded coding that will always be used, and these "custom" codings are supplemental. that is not the case here.
…of preparing documentation in properties files. I don't want unused properties to exist and to say something like "oh this property exists but we don't use it please ignore" when we can just remove it. it's totally safe. for #171
… and functions as a part of preparing documentation in properties files. I don't want unused properties to exist and to say something like "oh this property exists but we don't use it please ignore" when we can just remove it. it's totally safe. for #171
…vation.Query and Observation.Strategy, as there is now only one version of the query used to get Observations (specifying Code is superfluous and unnecessary, and out of convention from how the rest of the properties are specified). for #171
@mattStorer mattStorer merged commit 23ec816 into master Feb 20, 2024
3 checks passed
@mattStorer mattStorer deleted the feature/issue171 branch February 20, 2024 17:46
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