Bugs found by CI/CD.
This commit is contained in:
parent
46926d54ca
commit
134c6976fa
|
@ -43,7 +43,7 @@ const container = (testItem: TemplateResult) => {
|
||||||
${testItem}
|
${testItem}
|
||||||
<ul id="toggle-message-pad" style="margin-top: 1em"></ul>
|
<ul id="toggle-message-pad" style="margin-top: 1em"></ul>
|
||||||
</div>`;
|
</div>`;
|
||||||
}
|
};
|
||||||
|
|
||||||
const testOptions = [
|
const testOptions = [
|
||||||
["funky", "Option One: The Funky One"],
|
["funky", "Option One: The Funky One"],
|
||||||
|
@ -55,13 +55,13 @@ export const ToggleGroup = () => {
|
||||||
// eslint-disable-next-line @typescript-eslint/no-explicit-any
|
// eslint-disable-next-line @typescript-eslint/no-explicit-any
|
||||||
const displayChange = (ev: any) => {
|
const displayChange = (ev: any) => {
|
||||||
document.getElementById(
|
document.getElementById(
|
||||||
"toggle-message-pad"
|
"toggle-message-pad",
|
||||||
)!.innerText = `Value selected: ${ev.detail.value}`;
|
)!.innerText = `Value selected: ${ev.detail.value}`;
|
||||||
};
|
};
|
||||||
|
|
||||||
return container(
|
return container(
|
||||||
html`<ak-toggle-group @ak-toggle=${displayChange}>
|
html`<ak-toggle-group @ak-toggle=${displayChange}>
|
||||||
${testOptions.map(([key, label]) => html`<option value="${key}">${label}</option>`)}
|
${testOptions.map(([key, label]) => html`<option value="${key}">${label}</option>`)}
|
||||||
</ak-toggle-group>`
|
</ak-toggle-group>`,
|
||||||
);
|
);
|
||||||
};
|
};
|
||||||
|
|
|
@ -8,7 +8,7 @@ The most common types are:
|
||||||
|
|
||||||
- [**Procedural**](./procedural.md): these are How To docs, the HOW information, with step-by-step instructions for accomplishing a task. This is what most people are looking for when they open the docs... and best practice is to separate the procedural docs from long, lengthy conceptual or reference docs.
|
- [**Procedural**](./procedural.md): these are How To docs, the HOW information, with step-by-step instructions for accomplishing a task. This is what most people are looking for when they open the docs... and best practice is to separate the procedural docs from long, lengthy conceptual or reference docs.
|
||||||
|
|
||||||
- **Conceptual**: these docs provide the WHY information, and explain when to use a feature (or when not to!), and general concepts behind the fature or functioanlity.
|
- **Conceptual**: these docs provide the WHY information, and explain when to use a feature (or when not to!), and general concepts behind the feature or functioanlity.
|
||||||
|
|
||||||
- **Reference**: this is typically tables or lists of reference information, such as configuration values, or most commmonly APIs.
|
- **Reference**: this is typically tables or lists of reference information, such as configuration values, or most commmonly APIs.
|
||||||
|
|
||||||
|
|
Reference in New Issue