An ordered comparison on a JSON number is unknown: make the rule prominent for pack authors

Open Beginner friendly
#299 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
69/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
documentation

Research direction

Read the operator section and authoring guide, then check the conformance vectors for an existing case covering ordered comparison with a JSON number. Add the rule and the input-side fix where authors encounter them, and add a vector if none covers it; done when the guidance explains why the condition becomes unknown and how to avoid it.

Written by the indexing model from the issue text.

Description

documentation

Observed. Ordered comparison is defined on decimal strings. A fact given as a JSON number makes the condition unknown, which escalates. Unless the runtime's comparable-facts switch is on, nothing reports why.

Ask. State the rule where authors meet it (the operator section and the authoring guide), with the one-line fix on the input side, and consider a conformance vector that pins it if none does.

Found in an end-to-end trial of the released binaries (spec 0.3.0). Found by writing packs and matrices against the published schema.

Dominant language
Python
Stars
5
Forks
6
Avg merge
4h 57m
Merged PRs (30d)
95

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Judgment-Pack/judgment-pack-spec

All issues in Judgment-Pack/judgment-pack-spec

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.