- Start Date: (fill in today's date, YYYY-MM-DD)
- RFC PR: (leave this empty)
Description of the proposed feature or proposed changes.
If the proposal requires changes to the current API or the creation of new ones, add a basic code example.
Please make sure to explain the motivation for this proposal. It means explaining the use case(s) and the functional feature(s) this proposal is trying to solve.
Try to only talk about the intent not the proposed solution here.
Describe the proposal in details:
- Explaining the design so that someone who knows Kanvas can understand and someone who works on it can implement the proposal.
- Think about edge-cases and include examples.
What potential tradeoffs are involved with this proposal.
- Complexity
- Work load of implementation
- Can this be implemented outside of Kanvas's core packages
- How does this proposal integrate with the current features being implemented
- Cost of migrating existing Kanvas applications (is it a breaking change?)
- Does implementing this proposal mean reworking teaching resources (videos, tutorials, documentations)?
What are the alternatives?
Optional, but suggested for first draft proposals. What parts of the design are still TBD(To be defined)?