Skip to content

ArrayAccess::offsetExists on ParsedInput behaves as if on SafeInput #15

@Firehed

Description

@Firehed

This is a bit of an edge case, but it's entirely reasonable to check if the parsed data contains a value. Having the current restriction is only strictly valid for SafeInput, which has gone through the validation and re-shaping process.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions