microsoft / RulesEngine / 26694501520

95%

master: 97%

push

github

Batch-5: fix #668 STJ JsonElement unwrap, #676 docs cleanup, document #692 (#737)

for STJ, properties on an ExpandoObject built from JSON came through as
JsonElement values. Rule expressions like `input1.country == "india"` then
failed with "binary operator Equal is not defined for the types 'JsonElement'
and 'System.String'." Utils.CreateAbstractClassType now infers the native CLR
type from a JsonElement's ValueKind (string / int / long / double / bool /
null), and Utils.CreateObject unwraps JsonElement scalars to their native
values before assigning them. Objects and arrays inside the JsonElement keep
JsonElement shape — that path is for typed Newtonsoft-style models that
weren't using ExpandoObject anyway.

in JSON examples across README.md, docs/Getting-Started.md, and docs/index.md.
Removed.

after 5.0.4." That's actually standard C# Nullable<T> semantics — both
`null < x` and `null > x` are false. The pre-5.0.4 behavior was a
Newtonsoft / Dynamic.Core quirk, not the documented contract. Added an
explicit test documenting the current behavior plus the canonical
`!Dt.HasValue || Dt < someDate` workaround for users who want null-aware
ordering.

Not changed here: #679 (rule-chaining via @RuleName) is already covered
by in-flight PR #680 — no point duplicating that work. #710 and #709 are
unrelated AGV-themed spam; closing comments are in
issue-close-comments-batch-5.md.

All 164 unit tests pass on net6 / net8 / net9 / net10.

Co-authored-by: Yogesh Prajapati <yogeshcprajapati@outlook.com>

453 of 572 branches covered (79.2%)

11 of 22 new or added lines in 1 file covered. (50.0%)

832 of 878 relevant lines covered (94.76%)

679.36 hits per line