Skip to content

Parser: Escaped quote in unquoted value must throw. #6

Description

@ImrePyhvel
  1. Each field may or may not be enclosed in double quotes (however
    some programs, such as Microsoft Excel, do not use double quotes
    at all). If fields are not enclosed with double quotes, then
    double quotes may not appear inside the fields.

Repro steps: add 2 consecutive quotes within a value during parsing (Ex: my""value)
Current behavior: current parser (0.9.2) considers it an escaped quoting char (Ex: my"value)
Expected behavior: By RFC it must be invalid input instead. Exceptions should be thrown stating invalid input.

While current implementation can successfully parse wider range of documents, it is in conflict with RFC4180. As compliance is a main goal for the project then it can be considered a bug.

Added test TestUnquotedValueContaining2QuotesThrows to repro the issue.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions