[mayureshsonawane17]

Summary

This PR improves the documentation for in by:

1. Clarifying that accepts JSON dictionaries, lists, and scalar values.
2. Adding an explicit code example demonstrating partial matching with .

Test Plan

• Verified RST syntax and rendered documentation.

[sentry]

Bug: The documentation for json_params_matcher() claims support for all scalar values, but the implementation incorrectly handles falsy scalars (0, False, ""), treating them as an empty dictionary {}.
_{Severity: MEDIUM}

Suggested Fix

The implementation of json_params_matcher() should be updated to correctly handle falsy scalar values. Instead of relying on a truthiness check like param or {}, explicitly check if the parameter is None to decide whether to default to an empty dictionary. This will ensure that falsy values like 0, False, and "" are preserved and used for matching as documented.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: README.rst#L311

Potential issue: The documentation added at `README.rst:311` states that
`matchers.json_params_matcher()` supports scalar values. However, the implementation
uses a truthiness check that causes falsy scalar values like `0`, `False`, or `""` to be
coerced into an empty dictionary `{}`. Consequently, a user attempting to match a
request body containing a falsy scalar (e.g., `json_params_matcher(0)` for a body of
`"0"`) will experience a silent match failure, as the code will compare the parsed body
(`0`) against an empty dictionary (`{}`). This behavior contradicts the documentation.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[mayureshsonawane17]

Thank you for the review feedback! That is an accurate catch.

The underlying issue where falsy scalar JSON primitives (0, False, "", 0.0) are replaced with {} by (params or {}) in responses/matchers.py line 138 has been isolated and tracked in issue #834, with a dedicated fix and unit tests submitted in PR #836 (fix: preserve falsy scalar JSON primitives in json_params_matcher).

I have synchronized the documentation wording in this PR to align with the accepted parameter types while PR #836 resolves the implementation behavior.

[markstory]

There is a lint error introduced by these changes, could we get that addressed?