Motivation

Errors occurring during JSONPath operations are currently not reported accurately #11951. Additionally, error messages lack consistency across different JSONPath operations, such as those involving JSON templates and fields like InputPath, OutputPath, HeartbeatSecondsPath, etc.. Assembling these error messages is non-trivial, as it requires including the relevant field name. This update introduces logic to enhance the clarity and consistency of these error messages, as well as adding tests. A limitation of these changes are the execution history produced in the case of errors with TimeoutSecondsPath and HeartbeatSecondsPath, as these appear to be computed at a state level. However, the error messages are still corrcetly formatted and reported.

Changes

• jsonpath extraction logic is revised to raise a NoSuchJsonPathError exception which is reported in the absence of refined formatting logics
• the environment now keeps track of the field names being evaluated, which can be sampled by other logics to compose error messages
• EvalComponent objects now update the field they are evaluating in the environment
• Fields with custom error reporting logic implement their custom behaviour
• Default error reports for NoSuchJsonPathError
• minor change to next_state_name to ensure the reference to the program state instance being manipulated is not lost between it's validation and the action call