Basically creating custom markup based on the language provided. If it's a playground, we will nest the code inside a named <span>. This will allow developers to define custom code renderers that ecology can still interpret.
Here is an example for a loading state I intend to use inside the victory-docs:
Open to suggestions on how this might be improved. I'm a little shaky on using .getElementsByClassName("ecologyCode")[0] to get the DOM node with the code in it, but it seems like one solution.
Basically creating custom markup based on the language provided. If it's a playground, we will nest the code inside a named
<span>
. This will allow developers to define customcode
renderers that ecology can still interpret.Here is an example for a loading state I intend to use inside the victory-docs:
Open to suggestions on how this might be improved. I'm a little shaky on using
.getElementsByClassName("ecologyCode")[0]
to get the DOM node with the code in it, but it seems like one solution.cc @paulathevalley