Some path formats in intrinsic functions do not parse properly
Open
Nobody has claimed this yet.
bug
help wanted
- Dominant language
- Ruby
- Stars
- 0
- Forks
- 7
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 3
Description
Some odd forms of JSON path are not properly parsed by the path parser in intrinsic functions, and we need a more thorough json path parser to implement them. Even so, they are odd cases and are unlikely to occur in most real-world implementations. Those cases are defined in specs here:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the JSON path cases at spec/workflow/intrinsic_function/parser_spec.rb#L161-L163 and compare the expected odd path forms with the current parser behavior. Identify the parser entry point used by intrinsic functions, then extend coverage so those specified cases parse correctly and the parser specs pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100