Question 1

How to handle null values as undefined in Jiffy?

Accepted Answer

Use the {null_term, undefined} option in jiffy:decode/2 to replace JSON null with the atom undefined, aligning with Erlang conventions for missing data.

Question 2

Jiffy vs jsone: which is faster for JSON parsing?

Accepted Answer

Jiffy is generally faster due to its NIF implementation, but jsone is a pure Erlang alternative that avoids NIF risks, so the choice depends on performance versus safety trade-offs.

Question 3

How to encode Erlang maps to JSON with Jiffy?

Accepted Answer

Pass maps directly to jiffy:encode/1; for decoding, use the return_maps option in jiffy:decode/2 to convert JSON objects to maps on supported VMs.

Question 4

Does Jiffy support streaming JSON parsing?

Accepted Answer

No, Jiffy decodes entire JSON documents at once, which can be memory-intensive for large files, unlike streaming parsers that process data incrementally.

Question 5

What does the copy_strings option do in Jiffy?

Accepted Answer

It allocates new binaries for strings during decoding, preventing the decode result from keeping the original JSON data alive, which helps in memory management for long-running processes.

Question 6

Can Jiffy handle JSON with duplicate keys?

Accepted Answer

Yes, enable the dedupe_keys option in decode to ensure only the last value is retained, mirroring the behavior of most other JSON parsers.

jiffy

What is jiffy?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions