The "RFC" (request for comments) process is intended to provide a consistent and controlled path fornew features to enter the framework.
Many changes, including bug fixes and documentation improvements can be implemented and reviewed via thenormal GitHub pull request workflow.
Some changes though are "substantial", and we ask that these be put through a bit ofa design processand produce a consensus amongthe Vue core team andthe community.
A new feature that creates new API surface area Changing the semantics or behavior of an existing API The removal of features that are already shipped as part of the release channel. The introduction of new idiomatic usage or conventions, even if they donot include code changes to Vue itself. 创造新的API surface area 的feature 改变现有API的语义或行为 移除已经作为发布的一部分的功能 引入新的习惯用法或惯例,即使它们不包括对Vue本身的代码修改
The RFC life-cycle
1 2 3 4 5 6
An RFC goes through the following stages:
Pending: when the RFC is submitted as a PR. Active: when an RFC PR is merged and undergoing implementation. Landed: when an RFC's proposed changes are shipped in an actual release. Rejected: when an RFC PR is closed without being merged.