meson/test cases/failing/109 invalid fstring/test.json

{
    "stdout": [
        {
            "line": "test cases/failing/109 invalid fstring/meson.build:3:4: ERROR: Identifier \"foo\" does not name a variable."
        }
    ]
}
Add failing test cases & release snippet 4 years ago			`{`
			`"stdout": [`
			`{`
propagate the most accurate node to error messages During evaluation of codeblocks, we start off with an iteration of nodes, and then while evaluating them we may update the global self.current_node context. When catching and formatting errors, we didn't take into account that the node might be updated from the original top-level iteration. Switch to formatting errors using self.current_node instead, to ensure we can point at the likely most-accurate actual cause of an error. Also update the current node in a few more places, so that function calls always see the function call as the current node, even if the most recently parsed node was an argument to the function call. Fixes #11643 2 years ago			`"line": "test cases/failing/109 invalid fstring/meson.build:3:4: ERROR: Identifier \"foo\" does not name a variable."`
Formatting fix 4 years ago			`}`
Add failing test cases & release snippet 4 years ago			`]`
			`}`