Tony

> how do we determine what transformer to use on a mutate query? Could we stamp each collection or node with metadata which references the transformer used? That would limit...

I suppose we could also allow mutations to pass config args specifying which transformer to use for `CREATE` operations if they have multiple transformers for a single collection, or that...

> how do we know where to save the file if the content type has wildcards in the path? I think the default would be to place it at the...

> > Could we stamp each collection or node with metadata which references the transformer used? That would limit you to one transformer per collection in terms of CREATE operations....

>>I think the default would be to place it at the root-most common path which matches the wildcard. > >Can you elaborate on this? not sure I understand If someone...

> I'm almost tempted to say we should remove the * functionality and require named variable paths for everything Yeah I was thinking about if we should remove the glob...

> How do we create the slug? Does a slug make sense if it's not post / article data? Maybe this should be part of the config, an optional `slugField`...

maybe we could add a config option to encapsulate `CREATE` mutations? ```ts content: [ { path: '../../packages/flatbread/content/posts', collection: 'Post', refs: { authors: 'Author', }, onCreate: { slugField: 'title', }, },...

I agree it'd be best to have the provider declared in the config so that third-party providers can easily be registered. We might be able to get the provider out...

If we switch to a marker/keyword-based approach of parsing filters, we could avoid field name collision while also allowing objects to be passed as values: ```gql filter: { authors: {...