Open ewoutkramer opened 2 years ago
Although the chances are small that this influences current behaviour, doing this is a (minor) breaking change. Since it is also not really urgent, I will mark this issue as something to do for the next major release.
Describe the bug The extension method GetTypeProfiles on TypeReference (in ElementDefinitionExtensions.cs) does not work with the situation in R4+ where the TypeRef.Code can contain a FhirPath primitive type.
There must be zillions of places where we just assume TypeRef.Code is a string with just a FHIR type, but this is no longer the case.
Expected behavior I have written another implementation in the ElementSchema compiler:
Note that this also needs us to merge the Canonical type from the serverless validator project with the SDK Canonical type (a good idea anyway).