We have sysand.toml and workspace.json, and the more things they influence the more parts need to consider one or both. I want to ensure its clear what parts (sysand CLI, bindings, and other integrations) currently needs to consider what is in sysand.toml and .workspace.json.
With such clarity, we can determine the consequences of introducing configuration options.
As an example, maybe workspace.json currently is only needed to be read in some situations, but the introduction of some config feature forces it to be read by the CLI/bindings/intrgrations in every situation etc, its something we should be mindful about.
We have sysand.toml and workspace.json, and the more things they influence the more parts need to consider one or both. I want to ensure its clear what parts (sysand CLI, bindings, and other integrations) currently needs to consider what is in sysand.toml and .workspace.json.
With such clarity, we can determine the consequences of introducing configuration options.
As an example, maybe workspace.json currently is only needed to be read in some situations, but the introduction of some config feature forces it to be read by the CLI/bindings/intrgrations in every situation etc, its something we should be mindful about.