fix: return `null` for missig translations
Created by: Tirokk
Authored by roschaefer Merged
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.
🍰 Pullrequest
Issues
- None
Todo
-
None