Closed CCRalfvandenBurg closed 1 day ago
@CCRalfvandenBurg - We do not support creating custom resources today and hence you are seeing the behavior. Let us know if you have any further questions.
@EXPEkesheth would it be better to suggest a refactoring of the SearchOptionsFactory? The SearchOptionsFactory::Create method is quite long. To achieve custom resources the only option i see (and tested) is to copy and past the class/method.
Indeed there are more thinks that need to change to fully support custom resources ( the enum is used in multiple places). although with a little tweaking we got a few custom resources "working".
I think it would be a nice thing to have the ability to support custom resources. for our case a few hooks to achieve this with more easy would be nice.
@CCRalfvandenBurg - Refactoring can be suggested. It does not guarantee the change will be accepted, as it needs to go through review by the technical experts. We do not plan to support custom search parameters.
Closing with no further comments
Describe the bug The SearchOptionsFactory uses ResourceType enum. It will throw ResourceNotSupportedException when resource isn't matching value of the enum. This exception is throws for custom resources added to ModelInfoProvider
FHIR Version? Stu3/R4/R5
Data provider? CosmosDB/SQL Server
To Reproduce
Expected behavior A Bundle either empty or containing the item.
Actual behavior ResourceNotSupportedException is thrown. yielding a issue "Resource type 'Formulary' is not supported."