- Feature Name: (give your feature a unique name e.g., easy-updates)
- Start Date: (today's day, yyyy-MM-dd)
- Contributors:
- (Contributor name)
A paragraph describing the feature
Why should this feature be added? What issues does it help solve? What is the expected outcome?
If this proposal was already in the language, how might the documentation for this feature look? How would you explain this feature to another DataWeave user? Is this a continuation of an existing DataWeave pattern, or a new one? You may need to:
- Introduce new concepts
- Explain the feature in terms of a large number of examples
- How are error scenarios handled? What if the parameters passed are not as expected?
How does this feature work with existing supported data formats? For example, how does the feature work with XML namespaces and attributes?
Why should this feature not be implemented in DataWeave?
- What other designs have you considered and why did you not choose them?
- Why is this design better than alternatives?
- What is the impact of not adopting this change?
Discuss both the good and the bad of existing implementations of this feature, if applicable. A few examples:
- Does this feature exist in other programming languages? What experience has their community had?
- What lessons can we learn from existing implementations?
- Are there any papers or posts that already discuss this?
- What parts of the design do you expect to resolve through the RFC process before this feature gets implemented?
- What related issues do you consider out of scope for this RFC that could be address in the future?
- Have you considered how the feature will work outside of the scope of MuleSoft applications?
Rust RFC Template: https://github.com/rust-lang/rfcs/blob/master/0000-template.md Pony RFC Template: https://github.com/ponylang/rfcs/blob/master/0000-template.md