Future proofing composites

I’m currently building on ComposeDB and it’s been a great experience so far. But let’s say in the future I want to update my models to add new types and streams.

How would one migrate Composites from V1 to V2? Would I need to merge the composites of V1 and V2 and then deduplicate the data somehow?

I’m early in building but would love some context on how I can future proof my application.

1 Like

You can’t update models but you can add and remove models from your composites as wanted, so your overall application model can evolve as you need.
Composites act as sets of models so if you merge two composites using the same model for example, the model will only be present once in the resulting composite, if that’s what you mean by deduplicating data?

1 Like