[GH-ISSUE #2] Null property values in event callbacks #3

New issue

Closed

opened 2026-05-23 08:25:01 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-23 08:25:01 -06:00

Owner

Originally created by @appy-one on GitHub (Jan 28, 2021).
Original GitHub issue: https://github.com/appy-one/acebase/issues/2

Originally assigned to: @appy-one on GitHub.

When creating nodes that have properties with null values, events are triggered with the same objects, including the null property values.

Example:

const ref = db.ref('users')
ref.on('child_added', snap => {
    const user = snap.val();
    console.log(user.address); // null (expected: undefined)
});
ref.push({ name: 'Ewout', address: null });

null valued properties should be stripped from the objects for event callbacks

Originally created by @appy-one on GitHub (Jan 28, 2021). Original GitHub issue: https://github.com/appy-one/acebase/issues/2 Originally assigned to: @appy-one on GitHub. When creating nodes that have properties with null values, events are triggered with the same objects, including the null property values. Example: ```javascript const ref = db.ref('users') ref.on('child_added', snap => { const user = snap.val(); console.log(user.address); // null (expected: undefined) }); ref.push({ name: 'Ewout', address: null }); ``` null valued properties should be stripped from the objects for event callbacks