Skip to content

Bug: facet-json chokes on Byte-Order-Marker at beginning of file #1

@itsjunetime

Description

@itsjunetime

If a file contains a byte-order marker (at least U+FEFF) as the very first character in the file, facet-json doesn't understand it correctly and just returns an error.

I think it should essentially discard this byte and parse the rest of the file as if the byte didn't exist, but I guess I don't know the JSON spec so maybe this is explicitly forbidden and facet-json is doing the correct thing.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions