Message of the day:
Anything GraphQL and SilverStripe related.
likes GraphQL. The same API, but not the hassle of REST or SOAP
On a related note: I think we can probably get away with only one input type for create and update. Technically, update shouldn’t allow setting
id, but that’ll just lead to input type inflation if we create a new one specifically for update only. We could always move that validation to the resolver
@unclecheese Did you see my notes on pagination? https://github.com/silverstripe/silverstripe-graphql/issues/7. I don’t think it’ll influence your scaffolding work, but would be good if you sanity check that assumption. Basically, we’ll have a connection type returned instead of a direct list with the actual object type
As a user I want to read queries by page, so that I can open large folders. Acceptance criteria Asset List View is migrated to use GraphQL for fetching data Asset List view is paginated when data ...