fix form of questionnaireresponseitemanswer

[mharper-imaware]

json provided for mock questionnaireresponse item(https://www.hl7.org/fhir/questionnaireresponse-examples.html) would not parse into current structure. Fixed structure for QuestionnaireResponseItemAnswer

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[PontusNyberg]

Another way of doing this could be just adding a new struct instead of Extensions or leave extensions for that matter. A new struct that takes Value of *interface or maybe even a generic and a Type of *string where the type is described eg. "int64" or "bool".

[ivan-navi-studios]

The formatting does not align with the rest of the project. Besides that looks good

[mharper-imaware]

The formatting does not align with the rest of the project. Besides that looks good

@ivan-navi-studios what formatting needs to change?

[garywarner]

@mharper-imaware I think @ivan-navi-studios meant that it hadn't had go fmt run on it, so the tabbing and spacing was wrong... but I also think that was a github "moment", because it looks fine today and you haven't committed. Perhaps @ivan-navi-studios would be kind enough to take another look now?

For me, https://build.fhir.org/questionnaireresponse.html#QuestionnaireResponse.item has the answer as a backbone element, so it should have id, extension (from Element) and modifierExtension (from BackboneElement) as well as the individual answer I think. So, adding your new items and retaining the previous ones would be a solution.

I'd be keen to see this resolved as I use the library and next month's project involves a FHIR Questionnaire...

[PontusNyberg]

I realize my comment goes away from the fhir structure.
I agree with @garywarner, i would like to see the id, extension and modifierExtension added back then this merged. We're currently working with adding Questionnaires and its a bit annoying to add this whole structure because we're missing this PR.

[alexanderkiel]

Sorry, I've currently no time to look at this PR. Please fork if you like to have this feature.

[garywarner]

@alexanderkiel Just a note from myself (and reading other issues, many other people) to say thank you for the efforts in making this available to the Go FHIR community - it's really appreciated and I'm sure we all understand the pressures of work and other commitments.

[garywarner]

@mharper-imaware @PontusNyberg @ivan-navi-studios PR #7 to support polymorphic types resolves the underlying issue that this PR is attempting to resolve within the generator, rather than adding to the generated fields.

[PontusNyberg]

@garywarner Yes i've realized this. I've since then forked this repo and implemented that one.