sangria-graphql / sangria Goto Github PK

At the moment it is required to add message itself, but it is not very secure to rely on it

Now it should be possible to secure fields using the context + error handling mechanism. But maybe there are way to simplify this.

Interesting discussions:

• graphql/graphql-js#113

• Ensure that all merged field definitions have the same type and arguments
• document merging rules

Originally idea appeared here:

graphql/graphql-js#109

Maybe something more generic. For example similar to filers, which allow to this before and after of the execution of particular field

graphql/graphql-js@bd94446...cab585f

Also create test for sangria-specific features, like defers and projections

graphql/graphql-spec#55
graphql/graphql-spec@ac2f86e
graphql/graphql-spec#56

Hi,

I'm working on a Ruby GraphQL implementation and I'm exploring options for supporting efficient database queries. I really like your Projection approach and I've given it a try.

The problem I have is, what about Interfaces and Unions? In order to resolve the type, you need the object. But projection happens before getting the objects themselves.

I've been reading through your project but I must say Scala is a bit over my head :S Can you point me towards your solution for this issue, if you have one?

Thanks!

Hi,
How about having a gitter channel for this repo ..

Steps :
login to u r gitter account
-> create Room
-> choose Repository
-> done (gitter will send a automated PR )

(don't forget tests)

This probably will require additional project, something like sangria-marshaling-api. It then would be used by json integration libraries and sangria itself.

https://github.com/graphql/graphql-relay-js

graphql/graphql-js@2cf2f4c
https://github.com/graphql/graphql-js/pull/129/files

It will not be as helpful as in mutation operations, but at least it will affect field's subtree

• Give it all collected fields, bot only marked as Projection
• Projection now allows to customize the name
• NoProjection allows to remove field from projections list
• Projectior allows to specify how deep it should look (the level arg)

graphql/graphql-js@e7f7fee

• Introduce a type class for argument mapping
  • This type class should define unmarshaling mechanism
• OptionType should result in Option arg value

graphql/graphql-js#77
graphql/graphql-js#79
graphql/graphql-js#163
graphql/graphql-js#162

extendSchema utility: graphql/graphql-js#227