You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Data types that have no equivalent in JSON should be convertible to JSON using a configurable mechanism.
The obvious conversions mechanisms that we should provide by default are:
conversion of non-JSON data types to null
throwing an exception if an incompatible data type is encountered
custom conversion:
binary to base64 or something similar
UTCDate to integer
All of this should be configurable via options for the Dumper.
The text was updated successfully, but these errors were encountered:
date.toISOString() can also be desired for date objects. References and especially circular dependencies are probably best dealt with by substitution with null, although some special syntax could be introduced to later recover the inter references.
Data types that have no equivalent in JSON should be convertible to JSON using a configurable mechanism.
The obvious conversions mechanisms that we should provide by default are:
null
All of this should be configurable via options for the Dumper.
The text was updated successfully, but these errors were encountered: