feat(table): replaced column-type of "row-header" with boolean row-header

[WinkeeFace]

Description

Replaced column-type of row-header with a boolean row-header in the ebay-table component. Updated the relevant Marko and JSON files to reflect this change.

Context

This change was made to simplify the handling of row headers and improve ARIA accessibility. The boolean row-header is more intuitive and aligns better with accessibility standards.

References

• Issue: #2313

Screenshots

N/A

[LuLaValva]

Well done, thanks @WinkeeFace! Just a few notes:

1. Those tests are failing because you didn't include rowHeader in the index.marko destructure here.
2. Since Marko 5 / eBayUI normalizes kebab-case to camelCase so both are accepted, that needs to be accommodated for in TypeScript. To do this, you can either add duplicate "row-header"?: boolean; and "column-type"?: ... types in the interface (probably not recommended), or you can switch everything to kebab-case and use WithNormalizedProps<> like we do for Input (preferred).
3. =true is implied in Marko attributes (same as HTML), so there are a few examples that can be simplified (I showed one example in a code comment)

[WinkeeFace]

Well done, thanks @WinkeeFace! Just a few notes:

1. Those tests are failing because you didn't include rowHeader in the index.marko destructure here.
2. Since Marko 5 / eBayUI normalizes kebab-case to camelCase so both are accepted, that needs to be accommodated for in TypeScript. To do this, you can either add duplicate "row-header"?: boolean; and "column-type"?: ... types in the interface (probably not recommended), or you can switch everything to kebab-case and use WithNormalizedProps<> like we do for Input (preferred).
3. =true is implied in Marko attributes (same as HTML), so there are a few examples that can be simplified (I showed one example in a code comment)

Thank you for the feedback! I'll make those corrections.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 21f9d1b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR