add dollar sign to acceptable router paths #1055
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe the PR
Add
$
to valid router paths for compatibility with HL7 FHIR standard.The FHIR standard uses $ to prefix operations against compliant endpoints. Section 3.2.0.1 of the FHIR specification gives a definition and an example. Allowing $ as a modifier would enable teams working in Go to output Swagger specifications for APIs that interact with FHIR endpoints and further the goal of greater healthcare data interoperability around the world.
More information about HL7 FHIR standard
HL7 is a multinational non-profit organization that defines interoperability and messaging standards for the healthcare industry. The following countries use an HL7 defined specification as the primary method for messaging between healthcare providers: United States, Canada, Mexico, Australia, New Zealand, India, Pakistan, United Kingdom, Finland, Sweden, Spain, Turkey and Switzerland.
Historically, HL7 has facilitated information exchange through the sharing of documents. With the creation of the FHIR standard, HL7 aims to bring healthcare data movement in line with modern internet practices by introducing a REST based approach to exchange only relevant information instead of whole documents.
Relation issue
This PR would resolve issue #1053