ClassNames not consistently applied across components.
Open
Nobody has claimed this yet.
bug
- Dominant language
- JavaScript
- Stars
- 6
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
There are cases where groundwork does not honor className props correctly allowing the consuming app to override / add css classes.
If you run across examples where this is happening, please add a note here so we can track down the offending components.
REDACTED relevant log output
Steps to Reproduce
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 files, components, tests, or reproducible example are named. Start by reviewing the component implementations for className handling and compare cases where consuming applications need to add or override CSS classes. Done means identifying the offending components and making their className behavior consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100