What is the proposed use of the cockpit "layout" features?

[loremipson]

Preface: I'm brand spanking new to cockpit, and have only been playing around with it for a few hours. My use-case on the front end is Gatsby V2.

When looking at the graphql queries for layout field types, this gets a bit tricky. Because we don't really know what the data structure will be, since the content pieces are all dynamically entered and could be different for each collection entry.

Curious if there's currently a way to handle this that I don't see in the readme. I imagine something with inline fragments in graphql?

[WhippetsAintDogs]

Hi @loremipson , I haven't tried the layout field myself. So naturally, it's not actually supported by the plugin. I'll have a look a this soon, stay tuned (any PR in that regard is also welcome) ☺

[patesson]

Part of Layout appears to come through already. I haven't tried all the components, but the text based ones work already, returning "'id', 'class', and 'text'. Images return the same but these values don't make sense for the, and I would image any custom components would have similar issues

[DigitalGoldfish]

I am not sure if you know this article already, It's the best explanation of the Layout field I could find. https://medium.com/@pierreberchtold/gatsby-cockpit-layout-field-e908f4dbd87b

[loremipson]

Would be great to get that layout parser in this plugin, as it seems gatsby-plugin-cockpit progress has ceased for now.

[DigitalGoldfish]

It seems to be a pattern with gatsby plugins for cockpit that they get abondoned after a short time gatsby-plugin-cockpit was the third I used and that ceased to be developed. I do hope this one survives ...

Back to the layout field ... as @POGRaphy said, parts of the layout fields are coming through already but the way they are currently added to the graphql schema is a dead end; it wouldn't be possible to write GraphQL queries that match every possible combination that can be in the inferred schema. gatsby-plugin-cockpit uses a GraphQLJson field to return the whole object without gatsby trying to infer a schema for it.
I had a look at the code today and I believe I can migrate it to this plugin without too much effort. I hope to find some time to create a PR over the weekend.

[DigitalGoldfish]

As promised - experimental support for the layout field type can be found in #14. It would be awesome if one of you can spend some time and test it.

[WhippetsAintDogs]

Support for Layout and Layout-grid added in version 1.0.14+. Closing this issue.

[WhippetsAintDogs]

Reopened this issue in order to add support for images and assets nested in Layout and Layout-grid field.