Skip to main content

Bug Tracker

Side navigation

#9104 closed bug (fixed)

Opened May 04, 2011 06:40PM UTC

Closed May 09, 2011 08:02AM UTC

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

Reported by: dane.soba@razum.si 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/

Attachments (0)
Change History (4)

Changed May 05, 2011 01:51PM UTC by dmethvin comment:1

component: unfiledcore
milestone: 1.next1.6.1
priority: undecidedblocker
status: newopen

Changed May 09, 2011 08:00AM UTC by jaubourg comment:2

owner: → jaubourg
status: openassigned

Changed May 09, 2011 08:00AM UTC by jaubourg comment:3

component: coredeferred

Changed May 09, 2011 08:02AM UTC by jaubourg comment:4

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