Opened 12 years ago
Closed 12 years ago
#9104 closed bug (fixed)
Returning null or undefined in a pipe filter function causes an exception
| Reported by: | 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:
Change History (4)
comment:1 Changed 12 years ago by
| Component: | unfiled → core |
|---|---|
| Milestone: | 1.next → 1.6.1 |
| Priority: | undecided → blocker |
| Status: | new → open |
comment:2 Changed 12 years ago by
| Owner: | set to jaubourg |
|---|---|
| Status: | open → assigned |
comment:3 Changed 12 years ago by
| Component: | core → deferred |
|---|
comment:4 Changed 12 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
Fixes #9104. Returning null or undefined in a pipe callback shouldn't end up throwing an exception. Silly, silly, me.