Vinit Pandit

Hii @Julian please check if this test matches the requirements for this issue ```json { "description" : "metaschemas test for patternProperties", "schema" : { "$schema": "https://json-schema.org/draft/2020-12/schema", "patternProperties":{ "a" : {"$ref"...

@Julian, I believe this one needs to be closed, as it seems to be realted to [this issue](https://github.com/json-schema-org/JSON-Schema-Test-Suite/issues/245), if I'm not mistaken.

@Julian, it appears that escape characters are not covered in RJP. Could I work on that, if I am not misunderstanding it?

Ex: [this](https://github.com/json-schema-org/JSON-Schema-Test-Suite/blob/57617f254a6734d5c64fa86fd3b08e8799970b25/tests/draft-next/optional/format/json-pointer.json#L80) and all subsequent tests are not covered in RJP.

Thanks for your reply @Julian and sorry for disturb. enjoy your vacataion :)

@Julian just one question , if i am not wrong RJP also need to be include the tests with escape characters which are in absolute json pointer ? like this...

If we format the JSON automatically, there is one drawback. For example, when someone wants to split the changes into 2 commits, all changes get included in one commit, as...

> However note that the `/items/$ref`, which still says `#/items/0` is now invalid. We first renamed `prefixItems` to `items`, so the `$ref` should have been updated to `#/prefixItems/0` too. I'm...

Hasn't this problem already been addressed with the pattern ```json "pattern": "/items/\\d+" "$eval": "replace(schema['$ref'], '/items/(\\d+)', '/prefixItems/$1')" ``` or is there a possibility that this approach might not cover all cases?...

```json { "$schema": "https://json-schema.org/draft/2020-12", "$id": "https://example.com/anotherthing/agains/customer", "type": "object", "properties": { "name": { "type": "string" }, "phone": { "$ref": "/schema/common#/$defs/phone" }, "address": { "$ref": "/schema/address" } }, "$defs": { "https://example.com/schema/address": {...