Skip to content

no_match should point to erroneous tuple #4

@kpy3

Description

@kpy3

If one tries to encode large proplist, it is difficult to find property with error because jsonx always points to first tuple:
3> jsonx:encode([{<<"b">>, false},{<<"a">>, 999999999999999999999999999999999999999999999999999}]).
{no_match,{<<"b">>,false}}

Pointing to tuple with error makes error finding easier.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions