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
Describe the Issue
I think there is a possibility of someone wanting to re-initialize FhirEngine instance while still maintaining the same database. Few reasons:-
library enforced API changes in FhirEngineConfiguration. Application is forced to re-initialize the FhirEngine.
Application wants to sync to a different server. Application wants to re-initialize here.
But above or any changes in the FhirEngineConfiguration API will most likely lead to backward incompatibility.
We would need to do versioning to solve for this.
So that this does not become a breaking change in future, when FhirEngineConfiguration API is modified, we should decouple database instance from the FhirEngine instance creation.
Would you like to work on the issue?
The text was updated successfully, but these errors were encountered:
MJ1998
changed the title
Make FhirEngineConfiguration more readable
FhirEngineConfiguration should be accepted via a configuration file
Mar 2, 2024
MJ1998
changed the title
FhirEngineConfiguration should be accepted via a configuration file
FhirEngine instance should be decoupled from Database instance
Mar 5, 2024
MJ1998
changed the title
FhirEngine instance should be decoupled from Database instance
FhirEngine instance creation should be decoupled from Database instance
Mar 5, 2024
Describe the Issue
I think there is a possibility of someone wanting to re-initialize FhirEngine instance while still maintaining the same database. Few reasons:-
FhirEngineConfiguration
. Application is forced to re-initialize the FhirEngine.But above or any changes in the FhirEngineConfiguration API will most likely lead to backward incompatibility.
We would need to do versioning to solve for this.
So that this does not become a breaking change in future, when FhirEngineConfiguration API is modified, we should decouple database instance from the FhirEngine instance creation.
Would you like to work on the issue?
The text was updated successfully, but these errors were encountered: