Skip to content

Undocumented change to non-HTML escaped strings #365

Open
@RichardoC

Description

Can this behaviour please be documented and warned of in the main readme and function comments?

Current users might be relying on the sanitised return values and wouldn't be expecting this to change in a patch version.

28d458b

Thanks!

Activity

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

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