mirror of
https://github.com/slint-ui/slint.git
synced 2025-11-04 13:39: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
32 lines
1.1 KiB
Text
32 lines
1.1 KiB
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 SuperSimple := Rectangle {
|
|
// ^warning{':=' to declare a component is deprecated. The new syntax declare components with 'component MyComponent {'. Read the documentation for more info}
|
|
88;
|
|
// ^error{Parse error}
|
|
* / - + // no error there as this is already reported in the previous line
|
|
foo := Rectangle {
|
|
background: blue + 3
|
|
x: 45phx;
|
|
// ^error{Syntax error: expected ';'}
|
|
// FIXME: would be nice if the semicolon error was on the previous line
|
|
}
|
|
|
|
there was already parse error in this scope, so no more
|
|
|
|
property <string> xyz = 425;
|
|
// ^error{Syntax error: expected ';'}
|
|
|
|
Image {
|
|
* .
|
|
// ^error{Parse error}
|
|
}
|
|
};
|
|
// ^error{Extra semicolon. Remove this semicolon}
|
|
|
|
struct F {};
|
|
// ^error{Extra semicolon. Remove this semicolon}
|
|
|
|
export {F};
|
|
// ^error{Extra semicolon. Remove this semicolon}
|