[ ] Background: See if
<svg ... style="background-color: #000000;"...>...</svg> (in an .svg file) works in VS Code Markdown renderer (Works in Chrome, at least)
[ ] Foreground: Set path color with <path fill="#ffffff" ...>...</path>
Allow both colors to be configured in settings.json?
See if active VS Code theme can be loaded & its colors inspected (could be used to auto-determine icon preview colors: Used if no custom value provided in settings.json)
How to implement modifying the .svg images?
Write to a temp directory (default .svg images that come with the extension will be considered as template images)
Process images per request, name/identifier = {background}-{foreground}-{icon name}.svg
Or serve them somehow from a server? Probably a bad idea but a possibility.
Other benefits of processing the .svg images
Ability to set the size of the svg document = can actually place images inside of a Markdown table (extra image tag parameter syntax uses a vertical bar | which conflicts with Markdown table syntax)
Technically a generated .svg document could be used to provide a better documentation page (more compact layout)
[ ] Background: See if
<svg ... style="background-color: #000000;"...>...</svg>(in an .svg file) works in VS Code Markdown renderer (Works in Chrome, at least)[ ] Foreground: Set path color with
<path fill="#ffffff" ...>...</path>Allow both colors to be configured in settings.json?
See if active VS Code theme can be loaded & its colors inspected (could be used to auto-determine icon preview colors: Used if no custom value provided in settings.json)
How to implement modifying the .svg images?
Other benefits of processing the .svg images
|which conflicts with Markdown table syntax)