Skip to content

Commit c649070

Browse files
betrue-final-finalVesaJuvonen
betrue-final-final
authored and
VesaJuvonen
committed
Replaced ":" with "?" and updated beginning images to be shorter (SharePoint#934)
* Replaced ":" with "?" and updated beginning images to be shorter so they render larger on small windows. * Update column-formatting.md Corrected schema URL
1 parent 9eaa7df commit c649070

File tree

3 files changed

+21
-21
lines changed

3 files changed

+21
-21
lines changed

‎docs/declarative-customization/column-formatting.md

Lines changed: 21 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -75,15 +75,15 @@ The following image shows an example of conditional formatting applied to a numb
7575
![Severity warning of 70 with orange background](../images/sp-columnformatting-conditionalbasic.png)
7676

7777
This example customizes a number field to color that field red when its value less than 70. This example adds a style attribute to the parent `<div />` element, specifies a CSS class (`sp-field-severity--warning`) to apply to that item if the value inside the field is less than 70, and specifies no color if the value is outside that range (in which case it will use the default color for values in that list view).
78-
Note: this example uses a binary operation with the less than operator, "<", nested inside the conditional operation indicated by the operator, ":". Another description of the section in the following example is: If @currentField < 70 Then class = sp-field-severity--warning.
78+
Note: this example uses a binary operation with the less than operator, "<", nested inside the conditional operation indicated by the operator, "?". Another description of the section in the following example is: If @currentField < 70 Then class = sp-field-severity--warning.
7979

8080
```JSON
8181
{
8282
"elmType": "div",
8383
"txtContent": "@currentField",
8484
"attributes": {
8585
"class": {
86-
"operator": ":",
86+
"operator": "?",
8787
"operands": [
8888
{
8989
"operator": "<",
@@ -112,12 +112,12 @@ This pattern is useful when you want different values to map to different levels
112112
<!-- The schema URL will need to be updated when it is changed from customformatter to columnformatting -->
113113
```JSON
114114
{
115-
"$schema": "https://columnformatting.sharepointpnp.com/customFormatterSchema.json",
115+
"$schema": "http://columnformatting.sharepointpnp.com/columnFormattingSchema.json",
116116
"debugMode": true,
117117
"elmType": "div",
118118
"attributes": {
119119
"class": {
120-
"operator": ":",
120+
"operator": "?",
121121
"operands": [
122122
{
123123
"operator": "==",
@@ -133,7 +133,7 @@ This pattern is useful when you want different values to map to different levels
133133
},
134134
"sp-field-severity--good",
135135
{
136-
"operator": ":",
136+
"operator": "?",
137137
"operands": [
138138
{
139139
"operator": "==",
@@ -149,7 +149,7 @@ This pattern is useful when you want different values to map to different levels
149149
},
150150
"sp-field-severity--low",
151151
{
152-
"operator": ":",
152+
"operator": "?",
153153
"operands": [
154154
{
155155
"operator": "==",
@@ -165,7 +165,7 @@ This pattern is useful when you want different values to map to different levels
165165
},
166166
"sp-field-severity--warning",
167167
{
168-
"operator": ":",
168+
"operator": "?",
169169
"operands": [
170170
{
171171
"operator": "==",
@@ -199,7 +199,7 @@ This pattern is useful when you want different values to map to different levels
199199
},
200200
"attributes": {
201201
"iconName": {
202-
"operator": ":",
202+
"operator": "?",
203203
"operands": [
204204
{
205205
"operator": "==",
@@ -215,7 +215,7 @@ This pattern is useful when you want different values to map to different levels
215215
},
216216
"CheckMark",
217217
{
218-
"operator": ":",
218+
"operator": "?",
219219
"operands": [
220220
{
221221
"operator": "==",
@@ -231,7 +231,7 @@ This pattern is useful when you want different values to map to different levels
231231
},
232232
"Forward",
233233
{
234-
"operator": ":",
234+
"operator": "?",
235235
"operands": [
236236
{
237237
"operator": "==",
@@ -247,7 +247,7 @@ This pattern is useful when you want different values to map to different levels
247247
},
248248
"Error",
249249
{
250-
"operator": ":",
250+
"operator": "?",
251251
"operands": [
252252
{
253253
"operator": "==",
@@ -300,7 +300,7 @@ This example colors the current field red when the value inside an item's DueDat
300300
"txtContent": "@currentField",
301301
"style": {
302302
"color": {
303-
"operator": ":",
303+
"operator": "?",
304304
"operands": [
305305
{
306306
"operator": "<=",
@@ -325,7 +325,7 @@ To compare the value of a date/time field against a date that's not `@now`, foll
325325
"txtContent": "@currentField",
326326
"style": {
327327
"color": {
328-
"operator": ":",
328+
"operator": "?",
329329
"operands": [
330330
{
331331
"operator": "<=",
@@ -354,7 +354,7 @@ To compare a date/time field value against another date constant, use the **Date
354354
"txtContent": "@currentField",
355355
"style": {
356356
"color": {
357-
"operator": ":",
357+
"operator": "?",
358358
"operands": [
359359
{
360360
"operator": "<=",
@@ -461,7 +461,7 @@ This example applies `background-color` and `border-top` styles to create a data
461461
},
462462
"style": {
463463
"width": {
464-
"operator": ":",
464+
"operator": "?",
465465
"operands": [
466466
{
467467
"operator": ">",
@@ -511,7 +511,7 @@ This example relies on two number fields, `Before` and `After`, for which the va
511511
"elmType": "span",
512512
"attributes": {
513513
"class": {
514-
"operator": ":",
514+
"operator": "?",
515515
"operands": [
516516
{
517517
"operator": ">",
@@ -525,7 +525,7 @@ This example relies on two number fields, `Before` and `After`, for which the va
525525
]
526526
},
527527
"iconName": {
528-
"operator": ":",
528+
"operator": "?",
529529
"operands": [
530530
{
531531
"operator": ">",
@@ -536,7 +536,7 @@ This example relies on two number fields, `Before` and `After`, for which the va
536536
},
537537
"SortUp",
538538
{
539-
"operator": ":",
539+
"operator": "?",
540540
"operands": [
541541
{
542542
"operator": "<",
@@ -607,7 +607,7 @@ Creating custom column formatting JSON from scratch is simple if you understand
607607

608608
```JSON
609609
{
610-
"$schema": "https://columnformatting.sharepointpnp.com/customFormatterSchema.json"
610+
"$schema": "http://columnformatting.sharepointpnp.com/columnFormattingSchema.json"
611611
}
612612
```
613613
You now have validation and autocomplete to create your JSON. You can start adding your JSON after the first line that defines the schema ___location.
@@ -783,7 +783,7 @@ The following example shows the value of a style object. In this example, two st
783783
{
784784
"padding": "4px",
785785
"background-color": {
786-
"operator": ":",
786+
"operator": "?",
787787
"operands": [
788788
{
789789
"operator": "<",
@@ -848,7 +848,7 @@ The following example shows an Expression object that performs the following exp
848848

849849
```JSON
850850
{
851-
"operator": ":",
851+
"operator": "?",
852852
"operands": [
853853
{
854854
"operator": ">",

‎docs/images/sp-columnformatting-all.png

1.1 KB
Loading

‎docs/images/sp-columnformatting-none.png

12.8 KB
Loading

0 commit comments

Comments
 (0)