- Proposal date: (in the format of YYYY-MM-DD)
- Affected version: (e.g. 1.2.0.X)
- Related Issues: (if any)
Briefly describe the feature.
Why do we need to make this change? What scenarios does it generally address? What will be the result of this change?
If the proposal adds or modifies an API, please specify the API specifications in the following format and provide a basic code example.
Parameter Name | Type | Mandatory | Description |
---|---|---|---|
For more API specifications, please refer to Interface.
Show a simple code snippet of API usage
Yes: The proposer is willing to implement the feature themselves after the proposal is approved;
No: After the proposal is approved, other developers in the community will need to help implement it;
Optional. Please explain to someone familiar with the implementation of hapjs how to implement this feature in hapjs or what steps are required to implement this feature.
Can we not implement this feature? Please consider:
- The investment required to implement this feature, including the complexity of the code, the increase in code size, and the manpower required to implement the feature.
- Whether this feature does not need to be provided by hapjs and developers using hapjs can even implement it better at the application layer.
- The impact on the established development habits of hapjs.
- The impact on the published versions and existing features, as well as the cost of user migration.
- The impact on other RFC proposals that have not yet been implemented.
Are there other options to implement this feature?
If we implement this proposal, is there any way to help developers adapt to this change better?