Bug Tracker


Ticket #9104 (closed bug: fixed)

Opened 3 years ago

Last modified 3 years ago

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:
Blocking: Blocked by:


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:


Change History

comment:1 Changed 3 years ago by dmethvin

  • Priority changed from undecided to blocker
  • Status changed from new to open
  • Component changed from unfiled to core
  • Milestone changed from 1.next to 1.6.1

comment:2 Changed 3 years ago by jaubourg

  • Owner set to jaubourg
  • Status changed from open to assigned

comment:3 Changed 3 years ago by jaubourg

  • Component changed from core to deferred

comment:4 Changed 3 years ago by jaubourg

  • Status changed from assigned to closed
  • Resolution set to fixed

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

Changeset: 8c13cfa805c0576a2f02f33beb9d15d73afd2d41

Please follow the  bug reporting guidlines and use  jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.


Add a comment

Modify Ticket

as closed

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.