Birkir Gudjonsson

Alright. I think we should make this configurable, I personally am in favor of Relay style query structure, but that shouldn't block us from making this happen. Either from Content...

You will get all sorts of issues with splitting content types into multiple tables. - Relationships between documents and other tables, like releases - It may look cleaner from from...

Prime supports 1-to-1, 1-to-many and many-to-many relationships. You can create two schemas that reference one or multiple instances of each other as a field. Example: ```graphql type Book { authors:...

Hey Good feature request. You can add a `whereType` to the document field: https://github.com/birkir/prime/blob/master/packages/prime-field-document/src/PrimeFieldDocument.ts Good template is the group field: https://github.com/birkir/prime/blob/master/packages/prime-field-group/src/PrimeFieldGroup.ts If you need to add something to the where...

Well, I doubt we will replace it completely, but we may implement them somehow. Contentful does this very well, so I may end up model it after them

I am probably going to include this in 0.3.0 in the form argument on each field. ```graphql query { Blog { title titleNL: title(locale:"nl") body(locale:"is") } } ``` Would this...

Ok. But how is that different from what we already have? ```graphql query { Blog(locale:"nl") { title body } } ``` I am starting to think that this ticket is...

Yes, this is for versioning. All documents have the two fields, `id` and `documentId`. `id` is the auto generated uuid of each row in the table. `documentId` is something I...

Yes, that's is the idea. It's still in @todo for external, because I haven't figured out what to do with unauthenticated users. But for internal we have this of course....

Most likely invalid JSON in your prime config. Extra comma or something?