Details
-
Type:
New Feature
-
Status:
In Progress
-
Priority:
Critical
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: 3.3 Documentation
-
Labels:None
-
Similar Issues:None
Description
This includes
- A general description of Mule expressions that makes it clear how they differ from Spring property placeholders
- A precise description of where Mule expressions are used in configurations
- A complete list of all the evaluators
- For each evaluator, a description of the meta-syntax it supports
- For each evaluator, a list of the expressions is supports
- An explanation of how to create custom evaluators
Acceptance Criteria
- Complete reference documentation for all expression types
- Sufficient examples tutorial documentation for users to be able to create correct expressions for the most common use cases
What is the acceptance criteria for this? I think maybe define a set of the most popular ways of using expressions in Mule and define the criteria that a user can identify that they can use an expression there and determine the correct expression syntax to use without having to execute the expression in your mule flow.