Relocate and clean up reset.scss of packages/web-forms
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- bootstrap, scss, typescript
Research direction
Inspect packages/web-forms/reset.scss and the apps/forms location, identifying which rules only override Central's Bootstrap styles. Compare the rendered UI before and after any cleanup, then perform visual regression checks on Android, iPhone, Chrome, Firefox, and Safari. Done means the reset is relocated, obsolete rules are removed safely, and component styles remain unchanged.
Written by the indexing model from the issue text.
Description
Description
Evaluate the feasibility of cleaning up reset.scss by keeping only what we need and relocating the file to apps/forms.
Some rules in reset.scss were specifically added to override Central's Bootstrap styles. Now that the apps are split, Bootstrap no longer affects Web Forms, meaning some of these defensive styles are obsolete.
The trickiest part will be conducting a highly detailed visual regression test. Because this file establishes the baseline for all styles built over time, we need to be extremely careful that pruning and moving these rules doesn't silently break the UI or alter our component styles.
The test should be completed in:
- Android
- IPhone
- Chrome
- Firefox
- Safari
- Dominant language
- TypeScript
- Stars
- 38
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing 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.
More from getodk/web-forms
-
iOS
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 3/5 Half a day Newbie friendliness 54/100
-
Offline send queueOpenIn Enketo
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Launch form offlineOpenneeds discussion
Difficulty 5/5 Over a week Newbie friendliness 38/100
All issues in getodk/web-forms
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
twilio/twilio-node#1241 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
hugomrdias/playwright-test#786 · 1 comment ·
Maintainers usually reply within 1 day
-
area:stdlib effort:S impact:med platform:linux type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
WenyuChiou/agent-board#1745 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day