{"id":13484568,"url":"https://github.com/reactjs/rfcs","last_synced_at":"2025-05-14T09:06:51.065Z","repository":{"id":37256342,"uuid":"113273337","full_name":"reactjs/rfcs","owner":"reactjs","description":"RFCs for changes to React","archived":false,"fork":false,"pushed_at":"2024-06-11T05:12:52.000Z","size":227,"stargazers_count":5520,"open_issues_count":40,"forks_count":558,"subscribers_count":572,"default_branch":"main","last_synced_at":"2024-10-29T14:25:20.304Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/reactjs.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE.md","code_of_conduct":"CODE_OF_CONDUCT.md","threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2017-12-06T05:32:51.000Z","updated_at":"2024-10-29T05:35:17.000Z","dependencies_parsed_at":"2023-02-05T17:05:13.625Z","dependency_job_id":"ec493970-d3fb-428e-8f80-dc987b1a1fd7","html_url":"https://github.com/reactjs/rfcs","commit_stats":{"total_commits":123,"total_committers":27,"mean_commits":4.555555555555555,"dds":0.6585365853658536,"last_synced_commit":"c15bc9df5afa8fd1dca6e5fd1c2ed073f7a9bd79"},"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/reactjs%2Frfcs","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/reactjs%2Frfcs/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/reactjs%2Frfcs/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/reactjs%2Frfcs/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/reactjs","download_url":"https://codeload.github.com/reactjs/rfcs/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":254110374,"owners_count":22016391,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-07-31T17:01:26.286Z","updated_at":"2025-05-14T09:06:51.046Z","avatar_url":"https://github.com/reactjs.png","language":null,"readme":"# React RFCs\r\n\r\nMany changes, including bug fixes and documentation improvements can be\r\nimplemented and reviewed via the normal GitHub pull request workflow.\r\n\r\nSome changes though are \"substantial\", and we ask that these be put\r\nthrough a bit of a design process and produce a consensus among the React\r\ncore team.\r\n\r\nThe \"RFC\" (request for comments) process is intended to provide a\r\nconsistent and controlled path for new features to enter the project.\r\n\r\n[Active RFC List](https://github.com/reactjs/rfcs/pulls)\r\n\r\n\r\n## Contributor License Agreement (CLA)\r\n\r\nIn order to accept your pull request, we need you to submit a CLA. You only need\r\nto do this once, so if you've done this for another Facebook open source\r\nproject, you're good to go. If you are submitting a pull request for the first\r\ntime, just let us know that you have completed the CLA and we can cross-check\r\nwith your GitHub username.\r\n\r\n**[Complete your CLA here.](https://code.facebook.com/cla)**\r\n\r\n## When to follow this process\r\n\r\nYou should consider using this process if you intend to make \"substantial\"\r\nchanges to React or its documentation. Some examples that would benefit\r\nfrom an RFC are:\r\n\r\n  - A new feature that creates new API surface area, and would\r\n     require a feature flag if introduced.\r\n  - The removal of features that already shipped as part of the release\r\n     channel.\r\n  - The introduction of new idiomatic usage or conventions, even if they\r\n     do not include code changes to React itself.\r\n\r\nSome changes do not require an RFC:\r\n\r\n  - Rephrasing, reorganizing or refactoring\r\n  - Addition or removal of warnings\r\n  - Additions that strictly improve objective, numerical quality\r\n  criteria (speedup, better browser support)\r\n  - Additions only likely to be _noticed by_ other implementors-of-React,\r\n  invisible to users-of-React.\r\n\r\n## What to expect\r\n\r\nIt is hard to write an RFC that would get accepted. Nevertheless, this shouldn't\r\ndiscourage you from writing one.\r\n\r\nReact has a very limited API surface area, and each feature needs to work seamlessly with all other features.\r\nEven among the team members who work on React full time every day, ramping up\r\nand gaining enough context to write a good RFC takes more than a year.\r\n\r\nIn practice, React RFCs serve two purposes:\r\n\r\n* **React Team RFCs** are submitted by [React Team members](https://reactjs.org/community/team.html) after extensive (sometimes,\r\nmulti-month or multi-year) design, discussion, and experimentation. In practice, they comprise the\r\nmajority of the RFCs that got merged so far. The purpose of these RFCs is to preview the design\r\nfor the community and to provide an opportunity for feedback. We read every comment on the RFCs\r\nwe publish, respond to questions, and sometimes incorporate the feedback into the proposal.\r\nSince our time is limited, we don't tend to write an RFC for a React feature unless we're very\r\nconfident that it fits the design. Although it might look like most React Team RFCs easily\r\nget accepted, in practice it's because 98% of ideas were left on the cutting room floor. The remaining\r\n2% that we feel very confident and have team consensus on about are the ones that we announce as RFCs for community feedback.\r\n\r\n* **Community RFCs** can be submitted by anyone. In practice, most community RFCs do not get merged.\r\nThe most common reasons we reject an RFC is that it has significant design gaps or flaws, does not work\r\ncohesively with all the other features, or does not fall into our view of the scope of React. However,\r\ngetting merged is not the only success criteria for an RFC. Even when the API design does not match\r\nthe direction we'd like to take, we find RFC discussions very valuable for research and inspiration.\r\nWe don't always review community RFCs in a timely manner, but whenever we start work on a related area, we check\r\nthe RFCs in that area, and review the use cases and concerns that the community members have posted.\r\nWhen you send an RFC, your primary goal should not be necessarily to get it merged into React as is,\r\nbut to generate a rich discussion with the community members. If your proposal later becomes accepted,\r\nthat's great. But even if it doesn't, it won't be in vain. The resulting discussion often informs the next\r\nproposal in the same problem space, whether it comes from the community or from the React Team. Many library\r\nauthors are reading the discussions, so RFCs often lead to community experimentation and userland solutions.\r\n\r\nWe apply the same level of rigour both to React Team RFCs and Community RFCs. The primary difference\r\nbetween them is in the design phase: React Team RFCs tend to be submitted at the end of the design\r\nprocess whereas the Community RFCs tend to be submitted at the beginning as a way to kickstart it.\r\n\r\n## What the process is\r\n\r\nIn short, to get a major feature added to React, one usually first gets\r\nthe RFC merged into the RFC repo as a markdown file. At that point the RFC\r\nis 'active' and may be implemented with the goal of eventual inclusion\r\ninto React.\r\n\r\n* Fork the RFC repo http://github.com/reactjs/rfcs\r\n* Copy `0000-template.md` to `text/0000-my-feature.md` (where\r\n'my-feature' is descriptive. Don't assign an RFC number yet).\r\n* Fill in the RFC. Put care into the details: **RFCs that do not\r\npresent convincing motivation, demonstrate understanding of the\r\nimpact of the design, or are disingenuous about the drawbacks or\r\nalternatives tend to be poorly-received**.\r\n* Submit a pull request. As a pull request the RFC will receive design\r\nfeedback from the larger community, and the author should be prepared\r\nto revise it in response.\r\n* Build consensus and integrate feedback. RFCs that have broad support\r\nare much more likely to make progress than those that don't receive any\r\ncomments.\r\n* Eventually, the team will decide whether the RFC is a candidate\r\nfor inclusion in React. Note that a team review may take a long time,\r\nand we suggest that you ask members of the community to review it first.\r\n* RFCs that are candidates for inclusion in React will enter a \"final comment\r\nperiod\" lasting 3 calendar days. The beginning of this period will be signaled with a\r\ncomment and tag on the RFCs pull request.\r\n* An RFC can be modified based upon feedback from the team and community.\r\nSignificant modifications may trigger a new final comment period.\r\n* An RFC may be rejected by the team after public discussion has settled\r\nand comments have been made summarizing the rationale for rejection. A member of\r\nthe team should then close the RFCs associated pull request.\r\n* An RFC may be accepted at the close of its final comment period. A team\r\nmember will merge the RFCs associated pull request, at which point the RFC will\r\nbecome 'active'.\r\n\r\n\r\n## The RFC lifecycle\r\n\r\nOnce an RFC becomes active, then authors may implement it and submit the\r\nfeature as a pull request to the React repo. Becoming 'active' is not a rubber\r\nstamp, and in particular still does not mean the feature will ultimately\r\nbe merged; it does mean that the core team has agreed to it in principle\r\nand are amenable to merging it.\r\n\r\nFurthermore, the fact that a given RFC has been accepted and is\r\n'active' implies nothing about what priority is assigned to its\r\nimplementation, nor whether anybody is currently working on it.\r\n\r\nModifications to active RFCs can be done in followup PRs. We strive\r\nto write each RFC in a manner that it will reflect the final design of\r\nthe feature; but the nature of the process means that we cannot expect\r\nevery merged RFC to actually reflect what the end result will be at\r\nthe time of the next major release; therefore we try to keep each RFC\r\ndocument somewhat in sync with the language feature as planned,\r\ntracking such changes via followup pull requests to the document.\r\n\r\n## Implementing an RFC\r\n\r\nThe author of an RFC is not obligated to implement it. Of course, the\r\nRFC author (like any other developer) is welcome to post an\r\nimplementation for review after the RFC has been accepted.\r\n\r\nIf you are interested in working on the implementation for an 'active'\r\nRFC, but cannot determine if someone else is already working on it,\r\nfeel free to ask (e.g. by leaving a comment on the associated issue).\r\n\r\n## Reviewing RFCs\r\n\r\nCurrently, the React Team cannot commit to reviewing RFCs in a timely manner.\r\nWhen you submit an RFC, your primary goal should be to solicit community feedback\r\nand generate a rich discussion. The React Team re-evaluates the current list of\r\nprojects and priorities every several months. Even if an RFC is well-designed,\r\nwe often can't commit to integrating it right away. However, we find it very\r\nvaluable to revisit the open RFCs every few months, and see if anything catches\r\nour eye. Whenever we start working on a new problem space, we also make sure\r\nto check for prior work and discussion in any related RFCs, and engage with them.\r\n\r\nWe read all RFCs within a few weeks of submission. If we think the design fits React well,\r\nand if we're ready to evaluate it, we will try to review it sooner. If we're hesitant about\r\nthe design or if we don't have enough information to evaluate it, we will leave it open\r\nuntil it receives enough community feedback. We recognize it is frustrating to not receive\r\na timely review, but you can be sure that none of the work you put into an RFC is in vain.\r\n\r\n## Inspiration\r\n\r\nReact's RFC process owes its inspiration to the [Yarn RFC process], [Rust RFC process], and [Ember RFC process].\r\n\r\n[Yarn RFC process]: https://github.com/yarnpkg/rfcs\r\n[Rust RFC process]: https://github.com/rust-lang/rfcs\r\n[Ember RFC process]: https://github.com/emberjs/rfcs\r\n\r\nWe've changed it in the past in response to feedback, and we're open to changing it again if needed.\r\n","funding_links":[],"categories":["Others","miscellaneous","Tools","rtfs"],"sub_categories":["redux 扩展"],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Freactjs%2Frfcs","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Freactjs%2Frfcs","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Freactjs%2Frfcs/lists"}