When using efsity to publish configs, only FHIR resources (everything with a resourceType) get published, which leaves out all the Binary resources such as
application config
sync config
navigation config
translation configs
registers
profiles
This issue is to track the publishing of the binary resources as well
extracts all the objects with references to a binary resource, together with the identifier.value
from the objects we have, search for those that the identifier.value matches application, sync or navigation, if found look for the mapping/matching file in the configs folder by searching for "value_config.json" e.g _applicationconfig.json
again from the objects we have, search for those that the identifier.value is or starts with the string "strings", this could be followed by an underscore and two characters. If found look for the mapping/matching file in the configs folder by searching for "value_config.json" e.g _strings_frconfig.json
finally from the objects we have, search for those that the identifier.value ends with the string "register" or "profile". If found, convert from camelCase to separated by underscores, then look for the mapping/matching file in the configs folder by searching for "value_config.json" e.g from ancRegister to _anc_registerconfig.json
take all the files found, encode them, then publish to the server using the binary id that is used in the object
When using efsity to publish configs, only FHIR resources (everything with a resourceType) get published, which leaves out all the Binary resources such as
This issue is to track the publishing of the binary resources as well