unclecheese

Ah, yeah, good point. This should have gone hand-in-hand with the CSRF fix. Would love a PR of that, @null

unclecheese

Still lots to do, though. Feel free to jump in and help! https://github.com/unclecheese/gatsby-poc/projects/1

Show 1 attachment(s)
GitHub  
unclecheese/gatsby-poc

Issue tracking for SS + Gatsby POC. Contribute to unclecheese/gatsby-poc development by creating an account on GitHub.

Hide attachment content
Conan

@unclecheese I have not tried Gatsby myself yet but looks promising, and I love SilverStripe so I'm really eager to try this out. It would also be fun to contribute to this package, I will look more into this 👍

unclecheese

But basically that, along with the silverstripe/silverstripe-gatsby SS module will build out your site in Gatsby with zero config. It just takes dataobject with a Link() function and stuffs it into a generated gatsby page, using the same template inheritance pattern as SSViewer.

unclecheese

Hey, @Conan! Thanks for your interest. A good place to start is the gatsby-starter-silverstripe starter. https://github.com/unclecheese/gatsby-starter-silverstripe

Show 1 attachment(s)
GitHub  
unclecheese/gatsby-starter-silverstripe

A starter for a Gatsby/Silverstripe CMS integration - unclecheese/gatsby-starter-silverstripe

Hide attachment content
unclecheese

FQCNs in templates are like the worst thing to ever happen in SS.

Mo

The other option was to add like 5 methods for each report (and I would have to add new methods each time a new report is added) or setup some sort of mapping on the DataObject

Mo

Both of which I couldn't be bothered to do! 😱

unclecheese

https://github.com/graphql/graphql-spec/issues/91

Show 1 attachment(s)
GitHub  
Recursively nested objects · Issue #91 · graphql/graphql-spec

Suppose we have a forum where users can reply to comments recursively: type RootQuery { message(id: String): Message messages: [Message] } type Message { id: String! content: String comments: [Mess...

Hide attachment content