These are chat archives for graphql-java/graphql-java

13th
Jun 2017
Daniel Ocampo
@danielocampo2
Jun 13 2017 02:18
Hi @bbakerman , just wanted to check if I am missing something in my PR in order for it to be merged (since it is approved). Thanks!
Sanchay Javeria
@javeria2
Jun 13 2017 05:02
@kaqqao I actually don't need relay support
Brad Baker
@bbakerman
Jun 13 2017 05:02
@javeria2 - not but you can take the idea contained there and create a “PageInfo” type object as a return value
  • not == no
Sanchay Javeria
@javeria2
Jun 13 2017 05:05
Ah, sounds good!
Brad Baker
@bbakerman
Jun 13 2017 05:08
  someData(first: 10, after : “cursor”) {
       pageInfo {
          hasNextPage
      } 
     name
     age

}
so in that made up example you could have a very similar pagination system as Relay wihout being Relay compliant
to get “someData” you need to pass in pagination info
and you can ask for “pagination info” back
Sanchay Javeria
@javeria2
Jun 13 2017 05:25
Wow! Thank you so much. Just looked at the relay docs again and it makes a lot more sense now.
Sergei Egorov
@bsideup
Jun 13 2017 18:59
Hey folks. According to the spec, an interface must have at least one member. However, I have a use case where I need "marker interfaces" (the system is very pluggable and I really need them). WDYT if we introduce "loose" mode where we ignore empty interfaces? (yes, it breaks the spec, or.... relaxes it)
Brad Baker
@bbakerman
Jun 13 2017 22:51
@bsideup - how does a marker interface work in graphql terms. If I can never ask information from it as a consumer - whats the use case?
fragment frageName on Marker {
    # you cant do this??
}
I would be hestitant to allow the engine to break spec without a really solid use case
also can you raised a ticket to track this request