qt/qtdeclarative.git/tests/auto/qml/qqmllanguage/data/MyCompositeComponent.qml, branch dev Qt Declarative (Quick 2) qml: deprecate top-level components 2022-09-29T16:19:06+00:00 Sami Shalayel sami.shalayel@qt.io 2022-09-26T15:01:40+00:00 d8066adc55051e305e319bfcd7ded7afbd550418 Print a deprecation warning during the IR compilation in the qqmltypecompiler.cpp when a top-level capital-c-Component is found. Also fix all the tests in tst_qqmllanguage that use a top level component (either by wrapping those Components into Items or by removing the explicit redundant Component-wrapping). This implies also fixing the line numbers for Components in tests that got wrapped into an Item. [ChangeLog][QtQml][QQmlComponent] QQmlComponents in qml document roots or in inline component roots are deprecated. Types defined in qml documents or in inline components are automatically wrapped into QQmlComponents when needed: those types really should not be inside a Component{}. Fixes: QTBUG-106547 Change-Id: I00630b879f52f681c98a1d4b804e3505f175b9d6 Reviewed-by: Ulf Hermann <ulf.hermann@qt.io> 
Print a deprecation warning during the IR compilation in the
qqmltypecompiler.cpp when a top-level capital-c-Component is found.
Also fix all the tests in tst_qqmllanguage that use a top level
component (either by wrapping those Components into Items or by removing
the explicit redundant Component-wrapping). This implies also fixing
the line numbers for Components in tests that got wrapped into an Item.

[ChangeLog][QtQml][QQmlComponent] QQmlComponents in qml document roots
or in inline component roots are deprecated. Types defined in qml
documents or in inline components are automatically wrapped into
QQmlComponents when needed: those types really should not be inside a
Component{}.

Fixes: QTBUG-106547
Change-Id: I00630b879f52f681c98a1d4b804e3505f175b9d6
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
[new compiler] Fix auto component creation with composite types 2014-03-05T14:01:07+00:00 Simon Hausmann simon.hausmann@digia.com 2014-03-05T09:21:52+00:00 247f6a34d161f10c4f6d5d516b8bfb7043ca78a2 A binding like this property Component foo: SomeComposite {} should not do an implicit component insertion if SomeComposite is actually a component. The property assignment is compatible and can proceed normally. Fixes tst_qquickcanvasitem, but added a separate unit test for this case. Change-Id: I7221eebd38dba3f2a82b59341739b9b67211e352 Reviewed-by: Lars Knoll <lars.knoll@digia.com> 
A binding like this

    property Component foo: SomeComposite {}

should not do an implicit component insertion if SomeComposite is actually
a component. The property assignment is compatible and can proceed normally.
Fixes tst_qquickcanvasitem, but added a separate unit test for this case.

Change-Id: I7221eebd38dba3f2a82b59341739b9b67211e352
Reviewed-by: Lars Knoll <lars.knoll@digia.com>