Missing property¶
[missing-property] Binding a value to a non-existing property.
This warning category is spelled [missing-property] by qmllint.
Can’t assign to non-existent default property¶
What happened?¶
You assigned an object to a non-existing default property.
Why is this bad?¶
The QML engine can’t assign this object at runtime.
Example¶
To fix this warning, specify the property you want to bind to or, if you are the author of the type, mark a property as default:
Property does not exist¶
What happened?¶
You assigned an expression to a non-existing property.
Why is this bad?¶
The QML engine can’t assign this expression at runtime.
Example¶
To fix this warning, remove the binding or correct a possible typo:
Member not found on type¶
What happened?¶
You accessed a member in a field member expression that can’t be found by QML tooling. A field member expression is an expression of the form someId.someProperty.
The member might not exist at all, for example when you made a typo. Or it might exist at runtime (because it exists on a specific sub-type that is always present), but not on the statically declared type.
Why is this bad?¶
The QML tooling can’t find this member, meaning that features like go-to-definition and autocomplete won’t work. At runtime, there might be an error or you might get an incorrect result if the member really does not exist. There won’t be an error if the member actually always exist at runtime, however in that case there can still be a performance cost due to missed optimizations.
Example¶
Property does not actually exist¶
To fix this warning, remove the binding or correct a possible typo:
Property exists, but type is not precise enough¶
To fix this warning, cast the object you read from to the more specific type:
In the example, the declared type of messageView's currentItem property is Item, which has no sender property: sender is defined only in Message. Here, we know however that currentItem always contains a Message, so we can cast currentItem to Message using a type assertion .