JSON path to the marker or an attribute on a MarkerObject or Usj in the current
USJ document. Note that it seems you must use ['bracket notation'] rather than .dot notation
if there are symbols other than underscore in the property name
The catch-all template-literal member that matches anything starting $. subsumes every depth
member below it — a depth path starts $.content[ in both notations — so any such path
type-checks, and the per-depth members document the shapes this type is expected to carry rather
than enforcing a bound. ($['property'], a property directly on the document root, and the empty
string '' are the two members the catch-all does not cover, because neither starts $..) Eight
depths cover the shapes the editors render in practice (table → row → cell → note → char → nested
char → text is seven).
JSON path to the
markeror an attribute on a MarkerObject or Usj in the current USJ document. Note that it seems you must use['bracket notation']rather than.dotnotation if there are symbols other than underscore in the property nameThe catch-all template-literal member that matches anything starting
$.subsumes every depth member below it — a depth path starts$.content[in both notations — so any such path type-checks, and the per-depth members document the shapes this type is expected to carry rather than enforcing a bound. ($['property'], a property directly on the document root, and the empty string''are the two members the catch-all does not cover, because neither starts$..) Eight depths cover the shapes the editors render in practice (table → row → cell → note → char → nested char → text is seven).