Related models are empty objects instead of null when not found

I don’t know if there is a practical reason for this, but when using model.fetch({ withRelated: ['otherModel'] }), the results for rows that did not have an otherModel relation have the property otherModel set to {}, an empty object. Shouldn’t this field be set to null? And if not, why is an empty object the preferred representation of a non-existent relation over false, null or undefined?

[Nick-Riggs]

We’ve also encountered this. Here are some of my findings:

1. This only occurs when using the pagination plugin’s fetchPage method. fetch() works as expected.
2. This is a performance issue as fetchPage isn’t just attaching a empty object for the relation, it’s actually firing the queries against the database looking for null value relations. fetch() does not do this.

[douglasjunior]

This problem still persists in 1.0.0, 1.0.1 e 1.1.0, with fetchPage.

For example: If in a list one record has a relation, all others records has an empty property.

[
    {
        "name": "Douglas",
        "address": {
            "stree": "One"
        }
    },
    {
        "name": "Bruna",
        "address": { }
    },
    {
        "name": "Bel",
        "address": { }
    }
]

If no one has a relationship, then the relation property is omitted.

[
    {
        "name": "Bruna",
    },
    {
        "name": "Bel",
    }
]

cc @edvaldoszy