GitLab

To make sure
property color foo: "white"
is of type color, not string.

Done-with: ckamm

Done-with: ckamm

Task-number: QTCREATORBUG-1757

Task-number: QTCREATORBUG-1737
Reviewed-by: Erik Verbruggen

When reading the xml file describing the Qml types, we incorrectly
classified all functions as methods. They should be slots, since
otherwise qmldump couldn't have dumped them in the first place.

Task-number: QTCREATORBUG-1755
Reviewed-by: Erik Verbruggen

By actually storing the documents instead of only the root and id
environments.

Filtering them out has long since become unnecessary. It was used back
when JS files were sourced from Script elements - there they'd only
make the functions available. Now functions and variables are imported.

Task-number: QTCREATORBUG-1735
Reviewed-by: Erik Verbruggen

The type information is now generated at runtime.

Done-with: owolff

Task-number: QTCREATORBUG-1021
Reviewed-by: Roberto Raggi

Such as
property int foo: bar
property int bar: foo.

Task-number: QTCREATORBUG-1389
Reviewed-by: Roberto Raggi

Reviewed-by: Roberto Raggi

Reviewed-by: Christian Kamm

* Context::build was potentially dangerous. Link and ScopeBuilder
  went out of scope before their results stopped being used.
* ScopeBuilder: If no function scope object was found, don't add it.

Reviewed-by: Erik Verbruggen

The documentation requires having it there.

50cc55af broke it.

Reviewed-by: ossi

Reviewed-by: Erik Verbruggen

Reviewed-by: Roberto Raggi

Done-with: Erik Verbruggen

At least direct recursion with name="Foo" extends="Foo" is detected
and rejected.

Done-with: Erik Verbruggen

Done-with: Erik Verbruggen

This used to contain all functions declared in Script blocks. With them
gone, there's no reason to keep it.

Use ScopeBuilder.push(...) for the same functionality.

Reviewed-by: Erik Verbruggen

Means their members are now completed correctly.

Task-number: QTCREATORBUG-1132
Reviewed-by: Erik Verbruggen

Task-number: QTCREATORBUG-1021
Reviewed-by: Erik Verbruggen

Done-with: ckamm