You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/docs/config.md
+23Lines changed: 23 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,6 +41,7 @@ For example, this Vega spec includes light-gray axis grid lines by default:
41
41
-[Legend Properties](#legends)
42
42
-[Title Properties](#title)
43
43
-[Scale Range Properties](#scale-range)
44
+
-[Signals](#signals)
44
45
{: .column-list }
45
46
46
47
##<aname="view"></a>View Properties
@@ -463,3 +464,25 @@ This example sets new default color palettes.
463
464
```
464
465
465
466
[Back to Top](#reference)
467
+
468
+
469
+
##<aname="signals"></a>Signal Definitions
470
+
471
+
Configuration files may also contain signal definitions for the top-level scope of a Vega specification. The syntax is identical to[standard signal definitions](../signals/): an array of named signal objects. Adding signal definitions to a configuration can be useful for defining style variables (colors, font sizes, etc.) that may be used elsewhere within either the config or a spec itself. Signals directly defined within a specification itself take precedence over those defined in the configuration.
472
+
473
+
###Usage
474
+
475
+
To enable dynamic scaling of font sizes, one can define a signal that for a font size scale factor, then define other config entries relative to this value: