Actions
Bug #3870
closed![Author: Debbie Lockett](https://www.gravatar.com/avatar/9c2ec304a5bec55af709863d87d5f6b7?rating=PG&size=50&default=https%3A%2F%2Fassets.plan.io%2Fimages%2Fdefault_avatar.png)
![Assignee: Debbie Lockett](https://www.gravatar.com/avatar/9c2ec304a5bec55af709863d87d5f6b7?rating=PG&size=22&default=https%3A%2F%2Fassets.plan.io%2Fimages%2Fdefault_avatar.png)
Mishandled "undefined" in code for filter expression
Start date:
2018-08-02
Due date:
% Done:
100%
Estimated time:
Applies to JS Branch:
1.0, Trunk
Fix Committed on JS Branch:
1.0, Trunk
Fixed in JS Release:
SEF Generated with:
Platforms:
Company:
-
Contact person:
-
Additional contact persons:
-
Description
When filtering an iterator for an array, if the predicate is out of range (at run time) then this is not handled correctly. i.e. when input.expand()[subscript - 1]
returns undefined, we get an error. null
rather than undefined
should be supplied to Iter.Singleton()
.
Please register to edit this issue
Actions
Also available in: Atom PDF Tracking page