bug: JsonPathParserError in TimestampPath when any path fragments begin with a number

[attila]

bug: JsonPathParserError in TimestampPath when any path fragments begin with a number

[MEPalma]

Thank you for compiling this bug report! The issue appears to be related to some limitations to the JsonPath library that the StepFunctions interpreter relies on https://github.com/h2non/jsonpath-ng.
These are issues related to the same issue: #10603, #9937 (comment).
Nevertheless, we are looking into this limitation and I will be happy to update you as soon as a solution is implemented.

[TheDanGior]

I am seeing a similar bug when my JSON path starts with a symbol. The @class JSON path is included automatically by our library when serializing to JSON from Java.

Input:

{
    "@class":"com.company.name.InputData",
    "id":"123abc",
    "sourceUserId":"101",
    "inputFileS3Keys": [ "00000000-1111-2222-3333-444444444" ]
}

Error:

Exception=JsonPathParserError, Details=['Parse error at 1:1 near token $ ($)'] at '(StatePass| {'comment': None, 'input_path': (InputPath| {'input_path_src': '$$.Execution.Id'}, 'output_path': (OutputPath| {'output_path': '$'}, 'state_entered_event_type': 'PassStateEntered', 'state_exited_event_type': 'PassStateExited', 'result': None, 'result_path': (ResultPath| {'result_path_src': '$.id'}, 'parameters': None, 'name': 'EmbedId', 'state_type': <StateType.Pass: 20>, 'continue_with': <localstack.services.stepfunctions.asl.component.state.state_continue_with.ContinueWithNext object at 0x7f0820510550>}'