You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My company is looking into using more and more custom FHIR resources, So I'm looking to develop a source generator to auto generate the resource code based on the structure definition. My idea is that it will look for files with a name that ends with .StructureDefinition.json and then generate code from those files.
I tried my hand in this but I think this could work.
change namespace to be the same as the <assemblyname>.<folder.path> instead of the constant namespace. This should be a simple change. supported in latest change
nested enum and generic Code<T> property generation, I'm still trying to figure out how to get this to work. supported in latest change
I tried this for one of my sample projects which uses v4.3.0 of the Firely libraries and ran into issues related to the changes introduced in the latest 5.x Firely libraries (specifically the change in the FhirEnumerationAttribute).
If this source generator is to be publicly released, should we make the generated code adapt to the version of the Firely library? Or do we tie it to a specific/latest version available? The source generator library itself does not reference the Firely library, and this could lead to mistakes like what I encountered.
Activity
GinoCanessa commentedon Aug 15, 2023
Just wanted to comment that I have reviewing this on my list for next week. Thanks for the work so far!
almostchristian commentedon Aug 17, 2023
I tried this for one of my sample projects which uses v4.3.0 of the Firely libraries and ran into issues related to the changes introduced in the latest 5.x Firely libraries (specifically the change in the
FhirEnumerationAttribute).If this source generator is to be publicly released, should we make the generated code adapt to the version of the Firely library? Or do we tie it to a specific/latest version available? The source generator library itself does not reference the Firely library, and this could lead to mistakes like what I encountered.