LookupIn operations raise PathNotFound instead of PathInvalid when a syntactically incorrect path is used

Description

For example,

The last line should raise a PathInvalid error, it raises PathNotFound instead

The following failing FIT tests should pass after this is fixed:

  • pathInvalidGetLookup

  • pathInvalidCountLookup

  • pathInvalidExistsLookup

Environment

None

Release Notes Description

None

Activity

Show:

Dimitris Christodoulou August 17, 2023 at 11:32 AM

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Fix versions

Sprint

Story Points

Priority

Instabug

Open Instabug

Sentry

Zendesk Support

Created August 10, 2023 at 11:04 AM
Updated August 17, 2023 at 8:26 PM
Resolved August 17, 2023 at 8:26 PM
Instabug