@@ -44,9 +44,9 @@ Keys can use brackets to encode hierarchical structures such as arrays and objec
44
44
45
45
The key's name should ** not** be in quotes.
46
46
47
- Example of an array of JSON objects:
48
- ```
49
- object =
47
+ Example of an array of JSON objects:
48
+
49
+ ``` json
50
50
[
51
51
{
52
52
"a" : " b" ,
@@ -56,7 +56,7 @@ object =
56
56
"e" : {
57
57
"f" : " g"
58
58
}
59
- },
59
+ }
60
60
]
61
61
```
62
62
@@ -69,7 +69,8 @@ This array's query string representation would be: `object[0][a]=b&object[1][c]=
69
69
Array of tracks. Tracks are objects consisting of ` trackFile ` , ` trackType ` , and ` trackColorSettings ` .
70
70
71
71
A track object in JSON format might look like this:
72
- ```
72
+
73
+ ``` json
73
74
{
74
75
"trackFile" : " exampleData/internal/snp1kg-BRCA1.vg.xg" ,
75
76
"trackType" : " graph" ,
@@ -140,7 +141,8 @@ This array's query string representation would be: `object[0][a]=b&object[1][c]=
140
141
141
142
142
143
Examples of links:
143
- * Link with preexisting data:
144
+ * Link with preexisting data:
145
+
144
146
```
145
147
http://127.0.0.1:3001?
146
148
tracks[0][trackFile]=exampleData%2Finternal%2Fsnp1kg-BRCA1.vg.xg&
@@ -153,7 +155,8 @@ Examples of links:
153
155
dataType=built-in&
154
156
simplify=false
155
157
```
156
- * Link with custom data:
158
+ * Link with custom data:
159
+
157
160
```
158
161
http://127.0.0.1:3001?
159
162
tracks[1][trackType]=graph&
@@ -170,4 +173,4 @@ Examples of links:
170
173
region=ref%3A2000-3000&
171
174
dataType=mounted%20files&
172
175
simplify=false
173
- ```
176
+ ```
0 commit comments