manual:JSON
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| manual:JSON [2024/04/22 02:23] – peternlewis | manual:JSON [2026/05/13 02:47] (current) – [JSON] peternlewis | ||
|---|---|---|---|
| Line 13: | Line 13: | ||
| * `null` - null (missing or absent value) | * `null` - null (missing or absent value) | ||
| - | JSON terminology refers to dictionaries as “objects”, | + | JSON terminology refers to dictionaries as “objects”, |
| ===== JSON Paths ===== | ===== JSON Paths ===== | ||
| Line 19: | Line 19: | ||
| Keyboard Maestro introduces the concept of a JSON Path. This is similar to the concept of an XPath, and there are other similar but unrelated JSON path concepts around, and they have similar intentions, but none of these are the same, or have the same syntax. | Keyboard Maestro introduces the concept of a JSON Path. This is similar to the concept of an XPath, and there are other similar but unrelated JSON path concepts around, and they have similar intentions, but none of these are the same, or have the same syntax. | ||
| - | In Keyboard Maestro, for a variable named `J`, and JSON Path might look like: | + | In Keyboard Maestro, for a variable named `J`, a JSON Path might look like: |
| J[2+3].fieldname{%Variable%FieldName%} | J[2+3].fieldname{%Variable%FieldName%} | ||
manual/JSON.1713752630.txt.gz · Last modified: by peternlewis
