Closed larsgw closed 5 years ago
A replacer isn't an option unfortunately. New data types and cases like undefined have been addressed, and so has the abundance of comma's, so I guess this is fine for now. The warning is still included, but less visible due to less logging.
For some reason, I thought creating my own JSON serialiser was a good idea. It probably isn't:
143
undefined
still isn't handled properlySet
s,Map
s,Symbol
s etc. correctlyJSON.stringify()
function availableThe only issue is HTML (and arbitrary dict support) that won't work anymore, but I will have to find a different solution to that, possibly with a replacer function.