Following the introduction of the "config" attribute in #26, let's add a "vm" config option for "enableComponentSrcDataKey".
This is a feature that is helpful for local development and while inspecting elements. It helps devs figure out which widget is rendering. Notice data-component attribute in example below on nearbuilders.org:
Currently, this is hardcoded to "true" in the web component -- let's have this default to false and come from config instead.
Acceptance Criteria
[ ] Test validating no data-component present in DOM tree when false
[ ] Test validating data-component present when true
[ ] Add below excerpt to documentation under "Configuration Options"
{
"vm": {
// Configuration options for the VM
"features": {
"enableComponentSrcDataKey": boolean, // adds the "data-component" attribute specifying the rendered component's "src"
}
}
}
Following the introduction of the "config" attribute in #26, let's add a "vm" config option for "enableComponentSrcDataKey".
This is a feature that is helpful for local development and while inspecting elements. It helps devs figure out which widget is rendering. Notice data-component attribute in example below on nearbuilders.org:
Currently, this is hardcoded to "true" in the web component -- let's have this default to false and come from config instead.
Acceptance Criteria