js-composedb
js-composedb copied to clipboard
ceramicstudio
feat: expose flag to determine whether a composite is indexed
As pointed out by Spencer, I don't get what is the purpose for deploying without indexing? That would mean documents can be created but not queried on the node, which seems unlikely to be the wanted user experience?
The desired user behavior is to update their composite with additional indices for querying. That requires create without indexing. However, they may also run deploy, since this is the steps specified in docs, so if they do that, need to do so without indexing.
Just want to add some context here https://forum.ceramic.network/t/devtools-composite-frommodels-does-not-support-filter/1304
@PaulLeCam @stbrody The gist is we want to enable 2 workflows:
- define models/composite from scratch & deploy and index them (pretty clear)
- some other devs discover this model and would like to use it in their own application and as a result want to index these models and create new index definitions/composite (I think 2 is the confusing part)