-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: expose flag to determine whether a composite is indexed #196
base: main
Are you sure you want to change the base?
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,6 +5,7 @@ import { writeEncodedComposite } from '@composedb/devtools-node' | |
|
||
type Flags = CommandFlags & { | ||
output?: string | ||
deploy: boolean | ||
} | ||
|
||
export default class CompositeFromModel extends Command<Flags> { | ||
|
@@ -18,6 +19,12 @@ export default class CompositeFromModel extends Command<Flags> { | |
char: 'o', | ||
description: 'path to the file where the composite representation should be saved', | ||
}), | ||
deploy: Flags.boolean({ | ||
char: 'd', | ||
description: | ||
'Deploy the composite to the ceramic node, which will start indexing on the composite', | ||
default: true, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If I'm reading the code correctly, I believe this is a behavior change. I'm pretty sure There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good catch. That should default false. |
||
}), | ||
} | ||
|
||
async run(): Promise<void> { | ||
|
@@ -44,6 +51,7 @@ export default class CompositeFromModel extends Command<Flags> { | |
const composite = await Composite.fromModels({ | ||
ceramic: this.ceramic, | ||
models: allModelStreamIDs, | ||
index: this.flags.deploy, | ||
}) | ||
if (this.flags.output != null) { | ||
const output = this.flags.output | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -25,9 +25,13 @@ export function getDirPath(path: PathInput): string { | |
/** | ||
* Create a Composite from a GraphQL schema path. | ||
*/ | ||
export async function createComposite(ceramic: CeramicClient, path: PathInput): Promise<Composite> { | ||
export async function createComposite( | ||
ceramic: CeramicClient, | ||
path: PathInput, | ||
deploy: boolean, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That's a breaking API change, please set a default value or bump to v0.7 with docs updates. |
||
): Promise<Composite> { | ||
const file = await readFile(getFilePath(path)) | ||
return await Composite.create({ ceramic, schema: file.toString() }) | ||
return await Composite.create({ ceramic, schema: file.toString(), index: deploy }) | ||
} | ||
|
||
/** | ||
|
@@ -36,12 +40,12 @@ export async function createComposite(ceramic: CeramicClient, path: PathInput): | |
export async function readEncodedComposite( | ||
ceramic: CeramicClient | string, | ||
path: PathInput, | ||
index?: boolean, | ||
deploy: boolean, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is misleading, reading from JSON always deploys the models to the node anyway so only the indexing request is optional, please keep as-is. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It doesn't though. Composite create is the only command that creates (deploys) models to the node. |
||
): Promise<Composite> { | ||
const client = typeof ceramic === 'string' ? new CeramicClient(ceramic) : ceramic | ||
const file = getFilePath(path) | ||
const definition = (await readJSON(file)) as EncodedCompositeDefinition | ||
return Composite.fromJSON({ ceramic: client, definition: definition, index: index }) | ||
return Composite.fromJSON({ ceramic: client, definition: definition, index: deploy }) | ||
} | ||
|
||
/** | ||
|
@@ -112,7 +116,7 @@ export async function writeEncodedCompositeRuntime( | |
runtimePath: PathInput, | ||
schemaPath?: PathInput, | ||
): Promise<void> { | ||
const definition = await readEncodedComposite(ceramic, definitionPath) | ||
const definition = await readEncodedComposite(ceramic, definitionPath, false) | ||
const runtime = definition.toRuntime() | ||
await writeRuntimeDefinition(runtime, runtimePath) | ||
if (schemaPath != null) { | ||
|
@@ -130,7 +134,7 @@ export async function mergeEncodedComposites( | |
): Promise<string> { | ||
const sources = Array.isArray(source) ? source : [source] | ||
const composites = await Promise.all( | ||
sources.map(async (path) => await readEncodedComposite(ceramic, path)), | ||
sources.map(async (path) => await readEncodedComposite(ceramic, path, false)), | ||
) | ||
const file = getFilePath(destination) | ||
await writeEncodedComposite(Composite.from(composites), file) | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -236,7 +236,7 @@ export type FromModelsParams = CompositeOptions & { | |
* Whether to add the Models to the index or not. If `true`, the Ceramic instance must be | ||
* authenticated with an admin DID. Defaults to `false`. | ||
*/ | ||
index?: boolean | ||
index: boolean | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please keep this optional. |
||
} | ||
|
||
/** | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -46,6 +46,10 @@ Create an encoded composite definition from GraphQL [Composite Schema](https://d | |
|
||
You can find a detailed guide on the creation of Composites [here](https://developers.ceramic.network/docs/composedb/guides/data-modeling/composites) | ||
|
||
If updating your composite by specifying additional fields to filter on using the `createIndex` directive, run this | ||
command with `--no-deploy`. Your GraphQL definition will still be updated, but Ceramic will not attempt to re-index your | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
will not attempt to re-index the Models in your composite |
||
composite. For other updates to your composite, such as adding new models, run with `--deploy`. | ||
|
||
``` | ||
USAGE | ||
$ composedb composite:create INPUT | ||
|
@@ -57,6 +61,9 @@ OPTIONS | |
-c, --ceramic-url Ceramic API URL | ||
-k, --did-private-key DID Private Key (you can generate a fresh private key using composedb did:generate-private-key) | ||
-o, --output a path to file where the resulting encoded composite definition should be saved | ||
-d, --deploy Deploy the composite to the ceramic node, which will cause the node to start indexing the | ||
models contained within the composite | ||
--no-deploy Do not deploy the composite to the ceramic node | ||
``` | ||
|
||
### `composedb composite:models` | ||
|
@@ -117,6 +124,12 @@ available on the Ceramic Node that yor DApp connects to. You can find a detailed | |
guide on Composites' deployment | ||
[here](https://developers.ceramic.network/docs/composedb/guides/data-modeling/composites#deploying-composites) | ||
|
||
If updating your composite to add additional query fields, do not run this command. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. again, I think we need to be clearer with our language here about what exactly the problematic scenarios are and what the proper recourse is. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Did the language here get updated? I like the language you used for the |
||
It should only be run _the first time_ you add your composite to the Ceramic node. | ||
|
||
If you are reusing a model multiple times in different composites, you can also | ||
skip this command. | ||
|
||
``` | ||
USAGE | ||
$ composedb composite:deploy PATH | ||
|
@@ -126,6 +139,7 @@ ARGUMENTS | |
|
||
OPTIONS | ||
-c, --ceramic-url Ceramic API URL | ||
-k, --did-private-key DID Private Key (you can generate a fresh private key using composedb did:generate-private-key) | ||
``` | ||
|
||
### `composedb composite:compile` | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't feel super strongly about it, but I lean towards making create not deploy by default, so users have to explicitly deploy when they're ready. I think this will help with more complex situations where devs wants to create and merge multiple composites, possibly adding indices and views along the way, before finally deploying the final unified composite as the last step.
I could be swayed on this though if there's a case for why it's better to deploy by default
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, what does
composite:from-model
do? That one seems even more like it definitely shouldn't auto-deploy since you're likely to want to add indices to it before deploying. And if that one doesn't auto-deploy, then I feel like this shouldn't either just for consistency sake if nothing elseThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was doing this just to maintain the existing behavior, so this change won't suddenly cause things to "stop working" for users that aren't calling deploy.
I'm not entirely sure which way is better either.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
okay, I guess preserving existing behavior makes sense