[Bug]: No Mention of RFCs (or ANY Way to Provide Feedback) on Site
還沒有人認領這個 Issue。
- 主要語言
- JavaScript
- 星號
- 11.8k
- 分支
- 7.9k
- 平均合併
- 1 天 11 小時
- 30 天內合併 PR
- 11
描述
Summary
The React team (seems to?) prefer that new React suggestions be submitted through https://github.com/reactjs/rfcs/, rather than through GitHub issues.
That's totally reasonable, given the massive firehose of feedback you must get ... but can't you at least tell users? I had to find that link in a Reddit post 😢
I think it would make a lot more sense to link to it on https://react.dev/community ... not to mention on the GitHub Issue template (https://github.com/facebook/react/issues/new/choose), and probably a few other places too.
Page
Details
This doesn't need a ton of documentation; just something like:
To submit suggestions on React itself, first search the existing issues (link). If you can't find your suggestion there, submit it as a formal RFC (Request For Comment)(link).
貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
研究方向
從 react.dev/community 頁面和報告中連結的 GitHub issue template 開始。在提到的位置新增指向 React RFC process 以及相關 issue-search 或 feedback 指南的清楚連結，然後確認使用者能找到提交建議的位置。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- javascript, react
- 領域
- documentation
- Issue 類型
- 文件
- 難度
- 2/5
- 預估耗時
- 1-3 小時
- 活躍度
- 停滯
- 描述清晰度
- 描述清楚
- 新手友好度
- 45/100