Workflow for app-developers locally introducing schema and code changes

[diegoalexdiaz]

In some cases, app-developers need to introduce local changes to their application-schema (which is managed in a different github repo, and merged PRs publish npm dev packages for) while they work on their code. What’s the recommended workflow for them to:

1. Direct the code to use the local version of the schema (which they can also upload to a git-branch – but there’s no npm package for).
2. Ensure such local schema-changes won’t be accidentally overridden when they pull and build.

In C++, Bentley Build had the WIP_SCHEMAS env-var, which one could tweak locally to list any local copies of schemas that should be left alone while one pulled new code.

@ColinKerr replied:

It may be possible to make something work with Aruns cospaces: https://aruniverse.github.io/cospace/docs/getting-started/. Technically the bis-schemas repo publishes the schema packages that applications consume. So it may be possible to hook it’s build up with the studio app build. I have not tried this and it may not work but I’d be down to update the bis-schemas build if changes are needed.