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
Indeed this is a bug. We didn't notice that JSON only exposes encode_to_iodata! while Jason also exposes encode_to_iodata/1 (without the bang). I'll create a fix shortly.
I noticed failures in logs like such:
Turns out:
JSON
as a value for json_encoder configuration for postgrex,error-tracker
uses postgrex json_encoder to encode values,error-tracker
attempts to useencode_to_iodata/1
,encode_to_iodata!/1
(with a bang) isIt would be wonderful if error-tracker could support using JSON module.
The text was updated successfully, but these errors were encountered: