fullstack-development / fullstack-development/front-end-best-practices
Добавить пункт про баги в либах
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 336
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
Если в библиотеке есть бага/нерешенный вопрос из-за которого в проекте приходится писать костыль, то обязательно нужно оставить ссылку на ишью в репозитории либы
Например, кейс который ща у Лехи Жмайлика случился с тем что нативные focus/blur не всплывают, а у реакта какого-то фига всплывают (и эта штука висит с 2016 года) https://github.com/facebook/react/issues/6410#issuecomment-207064994
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
Find the checklist or guidelines section covering library workarounds; no file or test is named in the issue. Add a concise point requiring a link to the upstream library issue when a workaround is used, using the React focus/blur example and link as context. Done when the checklist states this practice clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100