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-11 15:22:59 +02:00
2019-10-14 16:42:11 +02:00
2019-11-05 00:06:15 +01:00
2019-11-06 18:32:25 +01:00
2019-11-05 00:06:15 +01:00
2019-08-02 14:26:06 +02:00
2019-09-20 16:52:12 +03:00
2019-05-31 19:31:39 +02:00
2019-05-31 19:31:39 +02:00
2019-11-11 08:52:04 +01:00
2019-11-05 18:06:10 +01:00
2019-11-06 18:32:25 +01:00
2019-11-05 18:06:10 +01:00
2019-10-18 12:54:55 +02:00
2019-10-21 13:25:56 +03:00
2019-08-02 14:26:06 +02:00
2019-10-14 16:46:37 +03:00
2019-10-14 15:17:49 -04:00
2019-10-03 16:39:32 +02:00