New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Empty hasOne relation should return null instead of {} when serialized #1839

merged 4 commits into from May 10, 2018


1 participant
Copy link

ricardograca commented May 9, 2018


When fetching a model that has a hasOne relation and that relation doesn't exist the relation should be null when serializing the model. Currently it's an empty object {}.


This makes the hasOne relationship behave like belongsTo which also exhibited this same unexpected behavior until it was changed with PR #1563. All other relation types continue working the same way, so a hasMany without any records is still an empty array [] when serialized.

This should make it easier to determine if a hasOne relation exists or not since after serialization you can just write:

if (model.singleRelation) { ... }

instead of:

if (model.singleRelation && { ... }

Proposed solution

This changes the eager pairing code to ensure that the relation creation part is skipped if the response from the SELECT query that tries to fetch the related data is empty. The eager pairing would run pushModels() which would always create relation data on the parent model, even when there is no data, resulting in the empty object that was present before this change.

This is a behavior similar to the belongsTo relation, except that that one can be determined much earlier in the eager loading code chain.

Fixes #1771.

Current PR Issues

This is a breaking change, but it shouldn't cause too much trouble since any existing conditions, as in the example above, will still continue working. Other use cases that attempt to add or read properties directly from the serialized output will break.

ricardograca added some commits May 9, 2018

Don't try to pair empty hasOne relations
- Since pushModels would still pair an empty model, corresponding to the
non-existant relation, with the parent model, the result was that when
serializing the parent model there would be an empty object for the
missing relation instead of the expected null value, like what happens
with belongsTo.

@ricardograca ricardograca added this to To Do in Version 0.14.0 via automation May 9, 2018

@ricardograca ricardograca moved this from To Do to In progress in Version 0.14.0 May 9, 2018

@ricardograca ricardograca merged commit 73b47dc into master May 10, 2018

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
continuous-integration/travis-ci/push The Travis CI build passed

Version 0.14.0 automation moved this from In progress to Done May 10, 2018

@ricardograca ricardograca deleted the rg-empty-hasone branch May 10, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment