Chokes on null values
See original GitHub issueA cell containing null
as the value throws an error (TypeError: Cannot read property 'toString' of null
). I’m not sure whether a more sensible default would be to stringify it to an empty string or to the string null
but it seems like either would be preferable to an error.
Issue Analytics
- State:
- Created 8 years ago
- Comments:14 (1 by maintainers)
Top Results From Across the Web
Spectral parsing chokes on unexpected null values #1981
Describe the bug. Spectral fails with Cannot read properties of null (reading 'in') and exit code 2 when you use null where spectral...
Read more >SQLServer update statement chokes on null value, even with ...
1 Answer 1 ... The problem is that the query is not returning any rows . . . hence producing a NULL value....
Read more >Java Bug System
stream.max/min chokes when max or min is null ... nullsLast or nullsFirst, one can treat nulls as the min or max of a...
Read more >Roller thinks 15 > 15 and chokes on 1d20+null | Roll20
First issue: Open dice roller. Enter 1d20+9 in the advanced field. Set target to > 15 and keep rolling till you get a...
Read more >JsonSerializerOptions.IgnoreNullValues Property
Gets or sets a value that indicates whether null values are ignored during serialization and deserialization. The default value is false.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Two year birthday for this issue! Just got bitten (using null as a default value of a pm2 module…).
doh. this is already fixed but not released on npm.
noticed as i was writing a fix