Follow the convention that constant enumerated values should be in ALLCAPS. This is a spec change for XVIZ, but retains compatibility with lowercase by forcing a case conversion at the appropriate places within the modules.
Spec change locations:
declarative ui properties
- component type
- layout
- interactions
xviz message
- type
- xviz/start
- session_type
- message_format
- log
- xviz/metadata
- stream metadata
- category
- scalar type, for time_series & variables
- primitive type, for time_series & variables
- annotation_type, for annotations
- stream style
- text_anchor
- text_baseline
- xviz/state_update
- update_type
- xviz/reconfigure
- update_type
This allows you to plot regions in an X, Y space, with defined upper
and lower Y bounds over a provided range of X values. These are
helpful when reasoning about particular complex optimization problems.
These are created by specifying the 3 XVIZ variable streams that
define the x coordinates, y minimum, and y maximum. These streams can
have multiple objects as long as the same objects exist on all
streams.
Styling is done by applying styles to the `x` variable stream objects.
The declarative UI plot component has a single "independentVariable" and
multiple "dependentVariables". In many places we forgot the "s".
That is not fixed with both the spec and the builder updated and tested.
This lets us validate declarative UI content before it gets sent to
the front end. Right now we are just going with camel case to match
the existing builders.
Declarative UI itself lets you generate panels from your XVIZ data
with no custom code.
