roschaefer deb4b4f698 fix: return null for missig translations
A query such as `{ notifications }` would return `null` for Locations
with a missing translation, e.g. `nameRU`. This would not happen for
queries implemented by `neo4j-graphql-js` because they nullify all
missing attributes automatically.
2019-11-12 19:14:34 +01:00
..
2019-10-02 00:54:01 +02:00
2019-11-06 21:42:34 +03:00
2019-10-04 01:39:18 +02:00
2019-11-10 11:48:39 +03:00
2019-07-13 19:26:56 +02:00