fix: allow using widget as primary control in XML View

[brentonhouse]

No description provided.

[build]

	Warnings
⚠️	Please ensure to add a changelog entry for your changes. Edit the CHANGELOG.md file and add your change under the Unreleased items header

	Messages
📖	✅ All tests are passing Nice one! All 3490 tests are passing.

Generated by 🚫 dangerJS against 5d4889e

[ewanharris]

This looks to have broken the use case here.

Maybe we only want to do code += '.getViewEx({recurse:true});\n'; when type === 'widget', and maintain the existing behaviour for all other use cases?

[brentonhouse]

This looks to have broken the use case here.

Maybe we only want to do code += '.getViewEx({recurse:true});\n'; when type === 'widget', and maintain the existing behaviour for all other use cases?

This seems to be a greater issue of a require/widget code generator not being aware that it is generating code inside of a Ti.UI.Tab element. Let me take a look and see if I can pass in some additional information from inside the compile/parsers/Ti.UI.Tab.js file. That way the require/widget can have enough context to generate properly.

[brentonhouse]

@ewanharris - I've added support for when widgets/require are in Tabs now

[ewanharris]

This change looks good to me. I'm going to hold off merging until we're post 8.0.0 just incase we have to rev Alloy for any found issues