PATH is not resolving correctly

Open

#285 opened on Nov 11, 2021 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 45/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: javascript
Domain: backend

Research direction

Reproduce issue #285 using the supplied rule and payloads, then review the linked Mojaloop discussion for context on the JSON-PATH behavior. The fix is done when a string body does not satisfy the $.amount condition, while an object body containing amount: '123' does, with regression coverage added in the appropriate project test.

Written by the indexing model from the issue text.

Description

I have seen some strange happenings with regard to how the JSON-PATH is resolving in the rules with "json-rules-engine": "6.1.2".

If you consider the following rule:

{
    "ruleId": 1,
    "description": "Returns an NDC exceeded error response (ML error 4001) from the simulator when transfer value is 123 in any currency",
    "conditions": {
        "all": [
            {
                "fact": "path",
                "operator": "equal",
                "value": "/transfers"
            },
            {
                "fact": "method",
                "operator": "equal",
                "value": "POST"
            },
            {
                "fact": "body",
                "operator": "equal",
                "value": "123",
                "path": "$.amount"
            }
        ]
    },
    "event": {
        "type": "simulateError",
        "params": {
            "statusCode": 500,
            "body": {
                "statusCode": "4001",
                "message": "Payer FSP insufficient liquidity"
            }
        }
    }
}

With the following payload:

{
  path: '/transfers',
  body: '123', // <-- Non-matching PATH
  method: 'POST',
}

The rule will still resolve and fire off the event which I believe is incorrect.

My expectation is that it should only resolve when the payload is as follows:

{
  path: '/transfers',
  body: {      // <-- correct body 
      amount: '123',  // <-- Matching PATH
  },
  method: 'POST',
}

Link for reference: https://github.com/mojaloop/mojaloop-simulator/pull/120/files#r747311386

Dominant language: JavaScript
Stars: 3.1k
Forks: 507
PR merge metrics: No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

Similar issues

[BUG] @mastra/inngest: errors thrown inside durable steps lose their original stack (and error type) — Inngest only sees the wrapper frame Open

bug customer-eng Durable Agents Inngest status: needs triage

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

mastra-ai/mastra#24748 · 1 comment · Opened Sep 22, 2026
[optimization:agents-md-curator] Trim and correct root ambient context in github/gh-aw-firewall (LOGGING.md dead link, stale test claim, ~12% context reduction) Open

optimization optimization:agents-md-curator

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

githubnext/gh-aw-cao#13475 · Opened Sep 22, 2026
[BUG]: "Clear All" in Settings doesn't clear the saved analysis, old data comes back after reload Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

AOSSIE-Org/OrgExplorer#253 · 1 comment · Opened Sep 22, 2026
isolated-declarations: TS9025 on an optional parameter property typed `readonly T[]`, which tsc 7 accepts Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

oxc-project/oxc#26944 · Opened Sep 22, 2026
bug report: ai observability - dry-running a paused evaluation emails the whole org Open

ai-observability bug team/ai-observability

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

PostHog/posthog#104687 · Opened Sep 22, 2026

More JavaScript issues