Skip to content

GraphQL parser swallows invalid escaped #2570

Closed
@pcarrier

Description

@pcarrier

The string generated by #2569 passes the graphql-js 15.0.0 parser just fine despite being invalid GraphQL. I would suggest being more conservative with invalid escape sequences even if it's a breaking change, this lets bad GraphQL loose.

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