Can you share the file where the violation breaks?
I would like to share an example but I need to create it since I don't want to post the actual source code.
Simply copying the problem mxml file under another name doesn't work because it is put outside its container and then the violation is not generated.
If I have to create an example it might be too time consuming to achieve these:
- keep the same component hierarchy
- keep the problem present
- keep the example clean from the real source code
That's why I wanted to get more info when this violation is triggered and hopefully create an example faster.
Could you, please provide the "threshold" that triggers this violation?
I would like to fix the problem but I don't know when it is detected.
The violation description says:
"This container is too deeply nested.. Nested containers can decrease application overall performance especially if they are in item renderers"
When a component is considered "too deeply nested"?
1 person found this helpful
After reviewing the code of this rule, it could work. I removed it form the trunk. I will work on it later on to see how we could build such a rule.
Sorry for that.