willvincent
05/30/2018, 9:10 PMid: !ID @unique
name: String!
geodata: String!
and geodata will store stringified json, and then when querying I want the resolver to manipulate that json data somehow, for sake of argument lets say manipulate it into valid geojson, but for reasons I’m not going to go into I don’t need or want an actual geojson field in the database for this data attribute.
How might one go about manipulating data in a resolver and similarly in a mutation, as it’s going into/coming out of the data store?Sam Jackson
05/30/2018, 9:19 PMJSON.parse then JSON.stringify in your resolver?Erik
05/30/2018, 9:20 PMSam Jackson
05/30/2018, 9:22 PMwillvincent
05/30/2018, 9:33 PMwillvincent
05/30/2018, 9:34 PMErik
05/30/2018, 9:39 PMwillvincent
05/30/2018, 10:42 PMSam Jackson
05/30/2018, 10:43 PMwillvincent
05/30/2018, 10:43 PM