- Start Date: YYYY-MM-DD
- RFC PR: -
- Issue: -
Disclaimer: This template is derived from the great RFC template that Yarn has come up with. (You may remove this disclaimer).
One paragraph explanation of the feature.
Why are we doing this? What use cases does it support? What is the expected outcome?
Please focus on explaining the motivation so that if this RFC is not accepted, the motivation could be used to develop alternative solutions. In other words, enumerate the constraints you are trying to solve without coupling them too closely to the solution you have in mind.
This is the bulk of the RFC. Explain the design in enough detail for somebody familiar with the UI5 linter to understand, and for somebody familiar with the implementation to implement. This should get into specifics and corner-cases, and include examples of how the feature is used. Any new terminology should be defined here.
What names and terminology work best for these concepts and why? How is this idea best presented?
Would the acceptance of this proposal mean the UI5 linter or any of its sub-components documentation must be re-organized or altered?
How should this feature be introduced and taught to existing UI5 linter users?
Why should we not do this? Please consider the impact on teaching people to use the UI5 linter, on the integration of this feature with existing and planned features, on the impact of churn on existing users.
There are trade-offs to choosing any path, please attempt to identify them here.
What other designs have been considered? What is the impact of not doing this?
This section should be removed (i.e. resolved) before merging
Optional, but suggested for first drafts. What parts of the design are still TBD? Are there any second priority decisions left to be made?