fix: emit CSS for enum-valued state variants without explicit value (#157)

[nathanacurtis]

Summary

When config.processing.states maps a prop to a concept without specifying a value (e.g. selected: { prop: selected }), enum-valued variants like Selected=Selected were silently skipped — only selected::true was registered in the lookup, so the enum value never matched and its styling never reached styles.css.

The fix registers the concept name itself as a secondary lookup key when no value is specified, and uses a case-insensitive fallback in the CSS transformer so Selected=Selected resolves to the selected concept and emits [aria-selected="true"].

Test coverage

• buildStateLookup now registers prop::conceptName in addition to prop::true when no value is configured; confirmed it does NOT add the extra key for explicit-value entries.
• New CSS transformer test: enum prop selected: { prop: 'selected' } emits [aria-selected="true"] for Selected=Selected, :indeterminate for explicit Indeterminate value, and skips the rest value Unselected.
• Regression test: boolean props (disabled::true) continue to work unchanged.

Closes#157

[nathanacurtis]

Closing — recreating with correct head branch (fix/css-enum-state-variants-157).

[nathanacurtis]

Summary

When config.processing.states maps a prop to a concept without specifying a value (e.g. selected: { prop: selected }), enum-valued variants like Selected=Selected were silently skipped — only selected::true was registered in the lookup, so the enum value never matched and its styling never reached styles.css.

The fix registers the concept name itself as a secondary lookup key when no value is specified, and uses a case-insensitive fallback in the CSS transformer so Selected=Selected resolves to the selected concept and emits [aria-selected="true"].

Test coverage

• buildStateLookup now registers prop::conceptName in addition to prop::true when no value is configured; confirmed it does NOT add the extra key for explicit-value entries.
• New CSS transformer test: enum prop selected: { prop: 'selected' } emits [aria-selected="true"] for Selected=Selected, :indeterminate for explicit Indeterminate value, and skips the rest value Unselected.
• Regression test: boolean props (disabled::true) continue to work unchanged.

Closes#157

[nathanacurtis]

Closing — recreating with correct head branch (fix/css-enum-state-variants-157).

[nathanacurtis]

Summary

When config.processing.states maps a prop to a concept without specifying a value (e.g. selected: { prop: selected }), enum-valued variants like Selected=Selected were silently skipped — only selected::true was registered in the lookup, so the enum value never matched and its styling never reached styles.css.

The fix registers the concept name itself as a secondary lookup key when no value is specified, and uses a case-insensitive fallback in the CSS transformer so Selected=Selected resolves to the selected concept and emits [aria-selected="true"].

Test coverage

• buildStateLookup now registers prop::conceptName in addition to prop::true when no value is configured; confirmed it does NOT add the extra key for explicit-value entries.
• New CSS transformer test: enum prop selected: { prop: 'selected' } emits [aria-selected="true"] for Selected=Selected, :indeterminate for explicit Indeterminate value, and skips the rest value Unselected.
• Regression test: boolean props (disabled::true) continue to work unchanged.

Closes#157

[nathanacurtis]

Closing — recreating with correct head branch (fix/css-enum-state-variants-157).

[nathanacurtis]

Summary

When config.processing.states maps a prop to a concept without specifying a value (e.g. selected: { prop: selected }), enum-valued variants like Selected=Selected were silently skipped — only selected::true was registered in the lookup, so the enum value never matched and its styling never reached styles.css.

The fix registers the concept name itself as a secondary lookup key when no value is specified, and uses a case-insensitive fallback in the CSS transformer so Selected=Selected resolves to the selected concept and emits [aria-selected="true"].

Test coverage

• buildStateLookup now registers prop::conceptName in addition to prop::true when no value is configured; confirmed it does NOT add the extra key for explicit-value entries.
• New CSS transformer test: enum prop selected: { prop: 'selected' } emits [aria-selected="true"] for Selected=Selected, :indeterminate for explicit Indeterminate value, and skips the rest value Unselected.
• Regression test: boolean props (disabled::true) continue to work unchanged.

Closes#157

[nathanacurtis]

Closing — recreating with correct head branch (fix/css-enum-state-variants-157).

[nathanacurtis]

Summary

When config.processing.states maps a prop to a concept without specifying a value (e.g. selected: { prop: selected }), enum-valued variants like Selected=Selected were silently skipped — only selected::true was registered in the lookup, so the enum value never matched and its styling never reached styles.css.

The fix registers the concept name itself as a secondary lookup key when no value is specified, and uses a case-insensitive fallback in the CSS transformer so Selected=Selected resolves to the selected concept and emits [aria-selected="true"].

Test coverage

• buildStateLookup now registers prop::conceptName in addition to prop::true when no value is configured; confirmed it does NOT add the extra key for explicit-value entries.
• New CSS transformer test: enum prop selected: { prop: 'selected' } emits [aria-selected="true"] for Selected=Selected, :indeterminate for explicit Indeterminate value, and skips the rest value Unselected.
• Regression test: boolean props (disabled::true) continue to work unchanged.

Closes#157

[nathanacurtis]

Closing — recreating with correct head branch (fix/css-enum-state-variants-157).

[nathanacurtis]

Summary

When config.processing.states maps a prop to a concept without specifying a value (e.g. selected: { prop: selected }), enum-valued variants like Selected=Selected were silently skipped — only selected::true was registered in the lookup, so the enum value never matched and its styling never reached styles.css.

The fix registers the concept name itself as a secondary lookup key when no value is specified, and uses a case-insensitive fallback in the CSS transformer so Selected=Selected resolves to the selected concept and emits [aria-selected="true"].

Test coverage

• buildStateLookup now registers prop::conceptName in addition to prop::true when no value is configured; confirmed it does NOT add the extra key for explicit-value entries.
• New CSS transformer test: enum prop selected: { prop: 'selected' } emits [aria-selected="true"] for Selected=Selected, :indeterminate for explicit Indeterminate value, and skips the rest value Unselected.
• Regression test: boolean props (disabled::true) continue to work unchanged.

Closes#157

[nathanacurtis]

Closing — recreating with correct head branch (fix/css-enum-state-variants-157).

[nathanacurtis]

Summary

When config.processing.states maps a prop to a concept without specifying a value (e.g. selected: { prop: selected }), enum-valued variants like Selected=Selected were silently skipped — only selected::true was registered in the lookup, so the enum value never matched and its styling never reached styles.css.

The fix registers the concept name itself as a secondary lookup key when no value is specified, and uses a case-insensitive fallback in the CSS transformer so Selected=Selected resolves to the selected concept and emits [aria-selected="true"].

Test coverage

• buildStateLookup now registers prop::conceptName in addition to prop::true when no value is configured; confirmed it does NOT add the extra key for explicit-value entries.
• New CSS transformer test: enum prop selected: { prop: 'selected' } emits [aria-selected="true"] for Selected=Selected, :indeterminate for explicit Indeterminate value, and skips the rest value Unselected.
• Regression test: boolean props (disabled::true) continue to work unchanged.

Closes#157

[nathanacurtis]

Closing — recreating with correct head branch (fix/css-enum-state-variants-157).

[nathanacurtis]

Summary

When config.processing.states maps a prop to a concept without specifying a value (e.g. selected: { prop: selected }), enum-valued variants like Selected=Selected were silently skipped — only selected::true was registered in the lookup, so the enum value never matched and its styling never reached styles.css.

The fix registers the concept name itself as a secondary lookup key when no value is specified, and uses a case-insensitive fallback in the CSS transformer so Selected=Selected resolves to the selected concept and emits [aria-selected="true"].

Test coverage

• buildStateLookup now registers prop::conceptName in addition to prop::true when no value is configured; confirmed it does NOT add the extra key for explicit-value entries.
• New CSS transformer test: enum prop selected: { prop: 'selected' } emits [aria-selected="true"] for Selected=Selected, :indeterminate for explicit Indeterminate value, and skips the rest value Unselected.
• Regression test: boolean props (disabled::true) continue to work unchanged.

Closes#157

[nathanacurtis]

Closing — recreating with correct head branch (fix/css-enum-state-variants-157).