Bug Tracker

Opened 6 years ago

Closed 6 years ago

#9104 closed bug (fixed)

Returning null or undefined in a pipe filter function causes an exception

Reported by: dane.soba@… Owned by: jaubourg
Priority: blocker Milestone: 1.6.1
Component: deferred Version: 1.6
Keywords: Cc:
Blocked by: Blocking:

Description

When null or undefined is returned inside a pipe filter function, an exception is thrown and no callbacks are called.

I would expect null to be returned as a result of the promise instead.

Here's a simple testcase:

http://jsfiddle.net/q6r4r/8/

Change History (4)

comment:1 Changed 6 years ago by dmethvin

Component: unfiledcore
Milestone: 1.next1.6.1
Priority: undecidedblocker
Status: newopen

comment:2 Changed 6 years ago by jaubourg

Owner: set to jaubourg
Status: openassigned

comment:3 Changed 6 years ago by jaubourg

Component: coredeferred

comment:4 Changed 6 years ago by jaubourg

Resolution: fixed
Status: assignedclosed

Fixes #9104. Returning null or undefined in a pipe callback shouldn't end up throwing an exception. Silly, silly, me.

Changeset: 8c13cfa805c0576a2f02f33beb9d15d73afd2d41

Note: See TracTickets for help on using tickets.