Tutorial: fix typos in examples and broken links
In the move example, the code uses `contacts` when the diagrams use `contact` (no 's') The code in the example: ``` Value contacts(kArrayType); // adding elements to contacts array. // ... o.AddMember("contacts", contacts, d.GetAllocator()); // deep clone contacts (may be with lots of allocations) // destruct contacts. ```
This commit is contained in:
parent
2f45319b4e
commit
0d62f5cd35
@ -18,7 +18,7 @@ digraph {
|
||||
|
||||
node [shape=Mrecord, style=filled, colorscheme=spectral7]
|
||||
|
||||
c1 [label="{contact:array|}", fillcolor=4]
|
||||
c1 [label="{contacts:array|}", fillcolor=4]
|
||||
c11 [label="{|}"]
|
||||
c12 [label="{|}"]
|
||||
c13 [shape="none", label="...", style="solid"]
|
||||
@ -41,13 +41,13 @@ digraph {
|
||||
|
||||
node [shape=Mrecord, style=filled, colorscheme=spectral7]
|
||||
|
||||
c2 [label="{contact:array|}", fillcolor=4]
|
||||
c2 [label="{contacts:array|}", fillcolor=4]
|
||||
c3 [label="{array|}", fillcolor=4]
|
||||
c21 [label="{|}"]
|
||||
c22 [label="{|}"]
|
||||
c23 [shape=none, label="...", style="solid"]
|
||||
o2 [label="{o:object|}", fillcolor=3]
|
||||
cs [label="{string|\"contact\"}", fillcolor=5]
|
||||
cs [label="{string|\"contacts\"}", fillcolor=5]
|
||||
c31 [label="{|}"]
|
||||
c32 [label="{|}"]
|
||||
c33 [shape="none", label="...", style="solid"]
|
||||
@ -59,4 +59,4 @@ digraph {
|
||||
c3 -> { c31; c32; c33 }
|
||||
}
|
||||
ghost -> o2 [style=invis]
|
||||
}
|
||||
}
|
||||
|
@ -19,7 +19,7 @@ digraph {
|
||||
|
||||
node [shape=Mrecord, style=filled, colorscheme=spectral7]
|
||||
|
||||
c1 [label="{contact:array|}", fillcolor=4]
|
||||
c1 [label="{contacts:array|}", fillcolor=4]
|
||||
c11 [label="{|}"]
|
||||
c12 [label="{|}"]
|
||||
c13 [shape=none, label="...", style="solid"]
|
||||
@ -42,13 +42,13 @@ digraph {
|
||||
|
||||
node [shape=Mrecord, style=filled, colorscheme=spectral7]
|
||||
|
||||
c2 [label="{contact:null|}", fillcolor=1]
|
||||
c2 [label="{contacts:null|}", fillcolor=1]
|
||||
c3 [label="{array|}", fillcolor=4]
|
||||
c21 [label="{|}"]
|
||||
c22 [label="{|}"]
|
||||
c23 [shape="none", label="...", style="solid"]
|
||||
o2 [label="{o:object|}", fillcolor=3]
|
||||
cs [label="{string|\"contact\"}", fillcolor=5]
|
||||
cs [label="{string|\"contacts\"}", fillcolor=5]
|
||||
c2 -> o2 [style="dashed", constraint=false, label="AddMember", style=invis]
|
||||
|
||||
edge [arrowhead=vee]
|
||||
@ -57,4 +57,4 @@ digraph {
|
||||
cs -> c3 [arrowhead=none]
|
||||
}
|
||||
ghost -> o2 [style=invis]
|
||||
}
|
||||
}
|
||||
|
@ -2,7 +2,7 @@
|
||||
|
||||
This tutorial introduces the basics of the Document Object Model(DOM) API.
|
||||
|
||||
As shown in [Usage at a glance](@ref index), a JSON can be parsed into DOM, and then the DOM can be queried and modified easily, and finally be converted back to JSON.
|
||||
As shown in [Usage at a glance](../readme.md#usage-at-a-glance), a JSON can be parsed into DOM, and then the DOM can be queried and modified easily, and finally be converted back to JSON.
|
||||
|
||||
[TOC]
|
||||
|
||||
@ -55,7 +55,7 @@ printf("hello = %s\n", document["hello"].GetString());
|
||||
~~~~~~~~~~
|
||||
|
||||
~~~~~~~~~~
|
||||
world
|
||||
hello = world
|
||||
~~~~~~~~~~
|
||||
|
||||
JSON true/false values are represented as `bool`.
|
||||
@ -65,7 +65,7 @@ printf("t = %s\n", document["t"].GetBool() ? "true" : "false");
|
||||
~~~~~~~~~~
|
||||
|
||||
~~~~~~~~~~
|
||||
true
|
||||
t = true
|
||||
~~~~~~~~~~
|
||||
|
||||
JSON null can be queryed by `IsNull()`.
|
||||
@ -74,7 +74,7 @@ printf("n = %s\n", document["n"].IsNull() ? "null" : "?");
|
||||
~~~~~~~~~~
|
||||
|
||||
~~~~~~~~~~
|
||||
null
|
||||
n = null
|
||||
~~~~~~~~~~
|
||||
|
||||
JSON number type represents all numeric values. However, C++ needs more specific type for manipulation.
|
||||
@ -526,11 +526,11 @@ Swapping two DOM trees is fast (constant time), despite the complexity of the tr
|
||||
|
||||
This tutorial shows the basics of DOM tree query and manipulation. There are several important concepts in RapidJSON:
|
||||
|
||||
1. [Streams](doc/stream.md) are channels for reading/writing JSON, which can be a in-memory string, or file stream, etc. User can also create their streams.
|
||||
2. [Encoding](doc/encoding.md) defines which character encoding is used in streams and memory. RapidJSON also provide Unicode conversion/validation internally.
|
||||
3. [DOM](doc/dom.md)'s basics are already covered in this tutorial. Uncover more advanced features such as *in situ* parsing, other parsing options and advanced usages.
|
||||
4. [SAX](doc/sax.md) is the foundation of parsing/generating facility in RapidJSON. Learn how to use `Reader`/`Writer` to implement even faster applications. Also try `PrettyWriter` to format the JSON.
|
||||
5. [Performance](doc/performance.md) shows some in-house and third-party benchmarks.
|
||||
6. [Internals](doc/internals.md) describes some internal designs and techniques of RapidJSON.
|
||||
1. [Streams](stream.md) are channels for reading/writing JSON, which can be a in-memory string, or file stream, etc. User can also create their streams.
|
||||
2. [Encoding](encoding.md) defines which character encoding is used in streams and memory. RapidJSON also provide Unicode conversion/validation internally.
|
||||
3. [DOM](dom.md)'s basics are already covered in this tutorial. Uncover more advanced features such as *in situ* parsing, other parsing options and advanced usages.
|
||||
4. [SAX](sax.md) is the foundation of parsing/generating facility in RapidJSON. Learn how to use `Reader`/`Writer` to implement even faster applications. Also try `PrettyWriter` to format the JSON.
|
||||
5. [Performance](performance.md) shows some in-house and third-party benchmarks.
|
||||
6. [Internals](internals.md) describes some internal designs and techniques of RapidJSON.
|
||||
|
||||
You may also refer to the [FAQ](doc/faq.md), API documentation, examples and unit tests.
|
||||
You may also refer to the [FAQ](faq.md), API documentation, examples and unit tests.
|
||||
|
Loading…
x
Reference in New Issue
Block a user