mirror of
https://github.com/slint-ui/slint.git
synced 2025-10-30 19:47:03 +00:00
12393e21bd
* syntax_tests: allow to "bless" tests, and don't use a regexp
A regexp was used at the beginning because I thought we would want to
allow error to contains things that were not predictable or that would
often change. But this is not the case¹. It is better to actually test
for the full error message
¹ well actually it was the case for path, but there is another substitution to
`📂` for the manifest directory
* syntax_tests: Bless the tests
* syntax_tests: Manual adjust after bless
Because there used to be comments on the same line of the message which
bless don't support
* Fix error message with path on windows
- The debug implementation of path make double slash, that's not what
we want to show the user
- normalize paths to use `/` so the test passes
22 lines
876 B
Text
22 lines
876 B
Text
// Copyright © SixtyFPS GmbH <info@slint.dev>
|
|
// SPDX-License-Identifier: GPL-3.0-only OR LicenseRef-Slint-Royalty-free-2.0 OR LicenseRef-Slint-Software-3.0
|
|
|
|
|
|
export component Foo {
|
|
in property <int> count;
|
|
|
|
for x in 0..count: Rectangle { }
|
|
// ^error{Cannot access the field 'count' of float. Range expressions are not supported in Slint, but you can use an integer as a model to repeat something multiple time. Eg: `for i in count`}
|
|
|
|
|
|
// In these case, we should not suggest to use a model with a count
|
|
|
|
property <float> invalid: 0..count;
|
|
// ^error{Cannot access the field 'count' of float}
|
|
|
|
for x in invalid.count: Rectangle { }
|
|
// ^error{Cannot access the field 'count' of float}
|
|
|
|
for x in 0.px.count: Rectangle { }
|
|
// ^error{Cannot access the field 'count' of length}
|
|
}
|