Skip to content

LiveObjects: consider how to handle backslashes in path segments #481

@lawrence-forooghian

Description

@lawrence-forooghian

Split from some review comments on #427.

A backslash is, as far as I'm aware, a valid character in a LiveMap key. So, does passing a path of a.b\.c.d to at() mean ["a", "b.c", "d"] or ["a", "b\", "c", "d"]? And, whichever one is the currently-specified behaviour (RTPO6b currently implies ["a", "b.c", "d"]), how do you get at() to give you the other one?

Bear in mind that the server REST API is also path-based so we'd ideally want to unify the logic.

Metadata

Metadata

Assignees

No one assigned

    Labels

    live-objectsRelated to LiveObjects functionality.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions