aboutsummaryrefslogtreecommitdiff
path: root/doc/ref/javascript/formatters.texi
diff options
context:
space:
mode:
authorHugo Hörnquist <hugo@lysator.liu.se>2022-03-15 01:14:45 +0100
committerHugo Hörnquist <hugo@lysator.liu.se>2022-03-15 01:43:12 +0100
commit2d35caa4b3e025a57c626f89c665da31ffbfe27d (patch)
treef22ad2d5c07626f116ca7c3a8762fd2fe68d6855 /doc/ref/javascript/formatters.texi
parentMake make-routes pre-compile all regexes. (diff)
downloadcalp-2d35caa4b3e025a57c626f89c665da31ffbfe27d.tar.gz
calp-2d35caa4b3e025a57c626f89c665da31ffbfe27d.tar.xz
Introduce concept of VEvent formatters in frontend.
Diffstat (limited to 'doc/ref/javascript/formatters.texi')
-rw-r--r--doc/ref/javascript/formatters.texi12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/ref/javascript/formatters.texi b/doc/ref/javascript/formatters.texi
new file mode 100644
index 00000000..65df48c4
--- /dev/null
+++ b/doc/ref/javascript/formatters.texi
@@ -0,0 +1,12 @@
+@node formatters
+@subsection formatters
+
+Formatting procedures used by some components.
+@c TODO can we have a backref of every node containing @ref{formatters-proc}?
+
+@deftypevar {Map<string, (e:HTMLElement, s:any) => void>} formatters
+@anchor{formatters-proc}
+
+Each procedure takes two arguments. The HTML-element which contents
+should be replaced, along with the target value, as returned by @ref{VEvent.getProperty}.
+@end deftypevar