Export ClassList type

[marvin-j97]

No description provided.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 600cb57

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

[coveralls]

Pull Request Test Coverage Report for Build 12679602027

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.2%) to 85.955%

---

Totals
Change from base Build 12660086976:	0.2%
Covered Lines:	2302
Relevant Lines:	2612

---

💛 - Coveralls

[ryansolid]

Is this the right place to export it. I wonder if it should be part of the JSX types? I'm suggesting that is the right answer I just really don't know what would be more expected.

[ryansolid]

Thinking this through. This type should probably be exposed from the JSX types in dom-expressions, since classList is part of the shared JSX attribute contract rather than a solid-js/web runtime API. In Solid it would ideally be consumed as JSX.ClassList via the generated JSX types, with classList?: ClassList inside JSX.CustomAttributes, instead of adding a separate top-level export from solid-js/web.