Update breakpoints
Open
Nobody has claimed this yet.
00-type/task
kind/proposal
- Dominant language
- TypeScript
- Stars
- 41
- Forks
- 16
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 3
Description
Welcome!
- Yes, I've searched similar issues on GitHub and didn't find any.
Description
Breakpoints currently used in faency is not aligned with radix nor with what we apply on other projects.
Set the breakpoints used in this project to be inline with radix breakpoints.
Contributor guide
No contributing guide indexed for this repository
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 locating the current breakpoint definitions in the Faency component library and compare their values with the linked Radix breakpoints documentation. The work is done when the project uses the aligned breakpoint values consistently; the issue does not mention a specific file or test to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100