slint/internal/compiler/tests/syntax/basic/tr.slint
Olivier Goffart 12393e21bd
syntax_tests: allow to update tests, and don't use a regexp (#8589)
* 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
2025-06-02 16:47:33 +02:00

38 lines
1.6 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 component X {
property <string> t1: @tr(boo);
// ^error{Expected plain string literal}
// ^^error{Syntax error: expected ';'}
// ^^^error{Parse error}
property <string> t2: @tr("boo\{t1}oo");
// ^error{Expected plain string literal}
// ^^error{Syntax error: expected ';'}
property <string> t3: @tr("boo" + "foo");
// ^error{Syntax error: expected ')'}
// ^^error{Syntax error: expected ';'}
property <string> t4: @tr("foo{}", t1);
property <string> t4: @tr("foo{}", t1 t2);
// ^error{Syntax error: expected ')'}
// ^^error{Syntax error: expected ';'}
property <string> c1: @tr("boo" => );
// ^error{Expected plain string literal}
// ^^error{Syntax error: expected ';'}
property <string> c2: @tr("boo" => "foo\{ff}");
// ^error{Expected plain string literal}
// ^^error{Syntax error: expected ';'}
property <string> e: @tr();
// ^error{Expected plain string literal}
// ^^error{Syntax error: expected ';'}
}