Orange-OpenSource / Orange-OpenSource/Orange-Boosted-Bootstrap
Remove too generic classes
Open
Nobody has claimed this yet.
🔍 study
css
🧩 enhancement
- Dominant language
- CSS
- Stars
- 219
- Forks
- 61
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 12
Description
Prerequisites
- I have searched for duplicate or closed feature requests
- I have read the contributing guidelines
Proposal
Search and remove classes like .back that is too generic to be easily searched and replaced and not enough to be self explanatory. .active is fine for example.
Motivation and context
Ease the future potential updates
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
Start by searching the repository for the .back class and other overly generic class names mentioned by the proposal, then inspect their usages and replacements. Done means the selected generic classes are removed and their references remain consistent, without changing unrelated class behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100