Merge pull request #25 from json-everything/schema/v8

updated docs

Author: gregsdennis

.jekyll-metadata

@@ -10,13 +10,13 @@ end
 
 # Windows and JRuby does not include zoneinfo files, so bundle the tzinfo-data gem
 # and associated library.
-platforms :mingw, :x64_mingw, :mswin, :jruby do
+platforms :windows, :jruby do
   gem "tzinfo", ">= 1", "< 3"
   gem "tzinfo-data"
 end
 
 # Performance-booster for watching directories on Windows
-gem "wdm", "~> 0.1.1", :platforms => [:mingw, :x64_mingw, :mswin]
+# gem "wdm", "~> 0.1.1", :platforms => [:mingw, :x64_mingw, :mswin]
 
 # Lock `http_parser.rb` gem to `v0.6.x` on JRuby builds since newer versions of the gem
 # do not have a Java counterpart.

Gemfile

@@ -62,12 +62,8 @@ There are three ways create pointers:
   ```c#
   var pointer = JsonPointer.Create("object", "and", 3, "arrays");
   ```
-- building with `Create<T>()` and supplying a LINQ expression (also see [below](#linq))
-  ```c#
-  var pointer = JsonPointer.Create<MyObject>(x => x.objects.and[3].arrays);
-  ```
 
-All of these options will give you an instance of the model that can be used to evaluate JSON data.
+Both of these options will give you an instance of the model that can be used to evaluate JSON data.
 
 ```c#
 using var element = JsonDocument.Parse("{\"objects\":{\"and\":[\"item zero\",null,2,{\"arrays\":\"found me\"}]}}");
@@ -121,43 +117,16 @@ Get the immediate parent:
 
 ```c#
 var pointer = JsonPointer.Parse("/objects/and/3/arrays");
-var parent = pointer[..^1];  // /objects/and/3
+var parent = pointer.GetParent();  // /objects/and/3
 ```
 
 Or get the local pointer (imagine you've navigated to `/objects/and/` and you need the pointer relative to where you are):
 
 ```c#
 var pointer = JsonPointer.Parse("/objects/and/3/arrays");
-var local = pointer[^2..];  // /3/arrays
+var local = pointer.GetLocal(2);  // /3/arrays
 ```
 
-There are also method versions of this functionality, which are also available if you're not yet using .Net 8: `.GetAncestor(int)` and `.GetLocal()`.
-
-> Accessing pointers acts like accessing strings: getting segments has no allocations (like getting a `char` via the string's `int` indexer), but creating a sub-pointer _does_ allocate a new `JsonPointer` instance (like creating a substring via the string's `Range` indexer).
-{: .prompt-info }
-
-### Building pointers using Linq expressions {#linq}
-
-When building a pointer using the `Create<T>()` method which takes a Linq expression, there are a couple of things to be aware of.
-
-First, JSON Pointer supports using `-` as a segment to indicate the index beyond the last item in an array.  This has several use cases including creating a JSON Patch to add items to arrays.
-
-Secondly, you have some name transformation options at your disposal.
-
-The first way to customize your pointer is by using the `[JsonPropertyName]` attribute to provide a custom name.  Since this attribute controls how System.Text.Json serializes the property, this attribute will override any other options.
-
-The second way to customize your pointer is by providing a `PointerCreationOptions` object as the second parameter.  Currently there is only the single option: `PropertyNamingResolver`.  This property is a function that takes a `MemberInfo` and returns the string to use in the pointer.  Several presets have been created for you and are available in the `PropertyNamingResolvers` static class:
-
-| Name | Summary |
-|---|---|
-| **AsDeclared** | Makes no changes. Properties are generated with the name of the property in code. |
-| **CamelCase** | Property names to camel case (e.g. `camelCase`). |
-| **KebabCase** | Property names to kebab case (e.g. `Kebab-Case`). |
-| **PascalCase** | Property names to pascal case (e.g. `PascalCase`). |
-| **SnakeCase** | Property names to snake case (e.g. `Snake_Case`). |
-| **UpperKebabCase** | Property names to upper kebab case (e.g. `UPPER-KEBAB-CASE`). |
-| **UpperSnakeCase** | Property names to upper snake case (e.g. `UPPER_SNAKE_CASE`). |
-
 ## Relative JSON Pointers {#pointer-relative}
 
 [JSON Hyperschema](https://datatracker.ietf.org/doc/draft-handrews-json-schema-hyperschema/) relies on a variation of JSON Pointers called [Relative JSON Pointers](https://tools.ietf.org/id/draft-handrews-relative-json-pointer-00.html) that also includes the number of parent and/or array-index navigations.  This allows the system to start at an internal node in the JSON document and navigate to another node potentially on another subtree.

_docs/pointer/basics.md

@@ -2,5 +2,5 @@
 title: __close
 permalink: /schema/:title/
 close: true
-order: "01.9"
+order: "01.10"
 ---

_docs/schema/basics.md

@@ -2,5 +2,5 @@
 title: __close
 close: true
 permalink: /schema/codegen/:title/
-order: "01.6.9"
+order: "01.07.9"
 ---

_docs/schema/close.md

@@ -3,7 +3,7 @@ layout: page
 title: Mini-Meta-Schema Reference
 permalink: /schema/codegen/:title/
 icon: fas fa-tag
-order: "01.6.3"
+order: "01.07.3"
 ---
 > **DEPRECATION NOTICE**
 >

_docs/schema/codegen/close.md

@@ -3,7 +3,7 @@ layout: page
 title: Supported Patterns
 permalink: /schema/codegen/:title/
 icon: fas fa-tag
-order: "01.6.2"
+order: "01.07.2"
 ---
 > **DEPRECATION NOTICE**
 >

_docs/schema/codegen/mini-meta-schemas.md

@@ -4,7 +4,7 @@ title: Generating Code from JSON Schema
 bookmark: Basics
 permalink: /schema/codegen/:title/
 icon: fas fa-tag
-order: "01.6.1"
+order: "01.07.1"
 ---
 > **DEPRECATION NOTICE**
 >

_docs/schema/codegen/patterns.md

@@ -3,5 +3,5 @@ title: __title
 bookmark: Code Generation
 permalink: /schema/codegen/:title/
 folder: true
-order: "01.6"
+order: "01.07"
 ---