A new argument handleMetadata should be supported in initWorkflow. By default it will be TRUE to handle both contacts and entities (The case of dictionary is now let aside as it's not yet subject to metadata validation). By setting this value to FALSE, we will be able to initialize a workflow, load software, etc, but without loading any contact and metadata.
Why this is needed? In the context of geoflow-shiny, a UI for metadata validation is proposed. When metadata are validated through this UI, and that metadata are handled by means of a software client, this metadata validation UI does require to load the configuration (through initWorkflow). In case of having metadata validation ERRORs (blocking), an initWorkflow that tries to load entities will fail. We then need to have the capacity to initialize the configuration without handling metadata contacts/entities, to delegate this to an UI.
A new argument
handleMetadatashould be supported ininitWorkflow. By default it will be TRUE to handle both contacts and entities (The case of dictionary is now let aside as it's not yet subject to metadata validation). By setting this value to FALSE, we will be able to initialize a workflow, load software, etc, but without loading any contact and metadata.Why this is needed? In the context of geoflow-shiny, a UI for metadata validation is proposed. When metadata are validated through this UI, and that metadata are handled by means of a software client, this metadata validation UI does require to load the configuration (through
initWorkflow). In case of having metadata validation ERRORs (blocking), aninitWorkflowthat tries to load entities will fail. We then need to have the capacity to initialize the configuration without handling metadata contacts/entities, to delegate this to an UI.cc @wheintz @mrouan