Greg Dennis

Expand on type of consensus

2

Currently, consensus is indicated with a simple ✔️. This is misleading when the consensus isn't "returns expected results." For example, Consensus for `$[?(@.d in [2, 3])]` is that the syntax...

Tests for root reference in filter expressions.

2

I found while answering a [StackOverflow question](https://stackoverflow.com/q/68516622/878701) that there aren't any tests checking for root reference in filter expressions: ``` $.SomeFieldB[?($.SomeFieldA == 'X')].SomeFieldC ``` for the JSON value ```json {...

Optionally return path to item instead of item itself

7

[Goessner's original post](https://goessner.net/articles/JsonPath/) declares that the return type (array form) could either be the found items or the JSON Paths to those items. Is there any intent to check for...

Test-Json: Use JsonSchema.Net (System.Text.Json) instead of NJsonSchema (Newtonsoft.Json)

28

# PR Summary Updates the `Test-Json` cmdlet to use [JsonSchema.Net](https://www.nuget.org/packages/JsonSchema.Net) instead of [NJsonSchema](https://www.nuget.org/packages/NJsonSchema) in order to: - use System.Text.Json instead of Newtonsoft - support the latest JSON Schema drafts (up...

Supporting later versions of JSON Schema

11

### Summary of the new feature / enhancement Hello! I'm on the JSON Schema specification team, and I was wondering what drafts are currently supported. I can see by and...

Annotation specification of `properties` could be improved

2

I had a realization today about what the text in [section 10.3.2.1](https://json-schema.org/draft/2020-12/json-schema-core.html#section-10.3.2.1) says about the annotation result of `properties` > The annotation result of this keyword is the set of...

I use this on my `json-everything` repo (and I've used in it a few other places) to track when PRs are dependent upon each other. For example, how #1285 is...

Depends on https://github.com/json-schema-org/json-schema-spec/pull/1085 I'll rebase this once ☝️ is merged. Updates the output schema file to match the new structure as described by the specification. Follow-up to #1249. I've tested...

Behavior around failed $ref resolution is not defined

20

(By "is not defined" I don't mean that it's considered and left as "undefined" behavior; I mean it's not addressed at all.) In [Slack](https://json-schema.slack.com/archives/CT7FF623C/p1660688416888499), we had a short discussion around...

Draft next

1

This is a placeholder for support of the next JSON Schema draft. This will be a new major version.