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

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:

Attachments (0)

Change History (4)

owner:	→ jaubourg
status:	open → assigned

component:	core → deferred

resolution:	→ fixed
status:	assigned → closed

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

Changeset: 8c13cfa805c0576a2f02f33beb9d15d73afd2d41

Side navigation