Details
-
Suggestion
-
Resolution: Unresolved
-
P3: Somewhat important
-
5.0.0
Description
Reading a non-existant property in JS does not trigger an error.
In contrast, writing to a non-existant property triggers an error like:
"Error: Cannot assign to non-existent property "fooBar""
Reading should trigger a similar error, as otherwise it is very easy to overlook coding errors.
See attached QML file for a testcase.
Tested with:
qtbase: v5.0.0-299-g3d9a400
qtjsbackend: v5.0.0-2-gce0de18
qtdeclarative: v5.0.0-35-gd89f1db
Attachments
Issue Links
- relates to
-
QTBUG-30069 strict/warning mode for QML development
-
- Open
-