react / react/react-strict-dom
Remove automatic camel-casing of CSS custom property names
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.6k
- Forks
- 206
- PR merge metrics
- No merged PRs in 30d
Description
Describe the issue
The original StyleX shim added camel-casing of CSS custom property names to ease internal adoption of native theme definitions that map to web theme definitions. However, custom properties are case sensitive, and we have now implemented the StyleX theming APIs. So we should remove this inconsistency and allow variable names to be case sensitive.
Expected behavior
Custom property names are case sensitive and do not get automatically camel cased.
Steps to reproduce
N/A
Test case
No response
Additional comments
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is identified in the issue. Locate the StyleX shim logic that automatically camel-cases CSS custom property names, then inspect the related tests or add focused coverage showing that names remain case sensitive. Done means custom property names are preserved exactly rather than camel cased.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100