kmandrup
06/15/2017, 10:15 AMkmandrup
06/15/2017, 10:16 AMagartha
06/15/2017, 10:27 AMyolen
06/15/2017, 2:11 PMmartin
06/15/2017, 2:49 PMkmandrup
06/15/2017, 4:17 PMjoao.santos
06/15/2017, 5:23 PMdk0r
06/15/2017, 5:43 PMnilan
06/15/2017, 7:25 PMmclovin
06/15/2017, 7:35 PMaurnik
06/15/2017, 7:48 PMmartin
06/15/2017, 8:52 PMyus
06/15/2017, 10:41 PMyus
06/15/2017, 10:41 PMyus
06/15/2017, 10:41 PMmartin
06/15/2017, 11:20 PMqsys
06/15/2017, 11:41 PMmartin
06/16/2017, 1:40 AMusers
that are connected in a social network? Or would that have to occur via a secondary data table?pbassut
06/16/2017, 1:47 AMtoken
from signinUser
mutation?ccannell
06/16/2017, 1:57 AMckelley
06/16/2017, 3:33 AMPerson
type and a Reminder
type, where a Reminder has a notifyDate: DateTime!
field. I want to sort the Person
type in order of the oldest notifyDate that they have as a reminder, so that the people with the "most expired" reminders are at the top. Currently my solution is to have a field on the person with a DateTime that re-stores the oldest reminder's notifyDate
, and every time I run a create or update on a Reminder I re-calculate it. Unfortunately, on Graphcool this requires that I add another round-trip query. Any ideas on a better way to structure?ckelley
06/16/2017, 3:47 AMvisualbbasic
06/16/2017, 5:55 AMvisualbbasic
06/16/2017, 5:56 AMimport Relay from 'react-relay'
export default class UpdatePokemonMutation extends Relay.Mutation {
getMutation () {
return Relay.QL`mutation{updatePokemon}`
}
getFatQuery () {
return Relay.QL`
fragment on UpdatePokemonPayload {
pokemon
edge
viewer {
allPokemons
}
}
`
}
getConfigs () {
return [
{
type: 'FIELDS_CHANGE',
fieldIDs: {
pokemon: this.props.pokemon
},
},
]
}
getVariables () {
return {
name: this.props.name,
url: this.props.url,
}
}
getOptimisticResponse () {
}
}
that's my fields_change mutationvisualbbasic
06/16/2017, 5:56 AMvisualbbasic
06/16/2017, 5:56 AMvisualbbasic
06/16/2017, 5:56 AMvisualbbasic
06/16/2017, 5:56 AMvisualbbasic
06/16/2017, 6:21 AMvisualbbasic
06/16/2017, 6:37 AM