Literal argument `'https://github.com/tempestphp/tempest-framework/blob/main/'` should be passed as a named argument for clarity. Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value. Help: Consider changing the call to `function_name(literal: 'https://github.com/tempestphp/tempest-framework/blob/main/')` instead of `function_name('https://github.com/tempestphp/tempest-framework/blob/main/')`.

Literal argument `'/'` should be passed as a named argument for clarity. Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value. Help: Consider changing the call to `function_name(literal: '/')` instead of `function_name('/')`.

Literal argument `'\\'` should be passed as a named argument for clarity. Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value. Help: Consider changing the call to `function_name(literal: '\\')` instead of `function_name('\\')`.

Literal argument `'packages/%s/src'` should be passed as a named argument for clarity. Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value. Help: Consider changing the call to `function_name(literal: 'packages/%s/src')` instead of `function_name('packages/%s/src')`.

Literal argument `"/^(\w+)/"` should be passed as a named argument for clarity. Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value. Help: Consider changing the call to `function_name(literal: "/^(\w+)/")` instead of `function_name("/^(\w+)/")`.

Literal argument `"{(b)?`#\[((?:\\\{1,2}\w+|\w+\\\{1,2})(?:\w+\\\{0,2})+)\]`}"` should be passed as a named argument for clarity. Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value. Help: Consider changing the call to `function_name(literal: "{(b)?`#\[((?:\\\{1,2}\w+|\w+\\\{1,2})(?:\w+\\\{0,2})+)\]`}")` instead of `function_name("{(b)?`#\[((?:\\\{1,2}\w+|\w+\\\{1,2})(?:\w+\\\{0,2})+)\]`}")`.

Literal argument `'createdAt'` should be passed as a named argument for clarity. Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value. Help: Consider changing the call to `function_name(literal: 'createdAt')` instead of `function_name('createdAt')`.

Literal argument `'payload'` should be passed as a named argument for clarity. Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value. Help: Consider changing the call to `function_name(literal: 'payload')` instead of `function_name('payload')`.

Literal argument `'eventClass'` should be passed as a named argument for clarity. Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value. Help: Consider changing the call to `function_name(literal: 'eventClass')` instead of `function_name('eventClass')`.

Literal argument `'uuid'` should be passed as a named argument for clarity. Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value. Help: Consider changing the call to `function_name(literal: 'uuid')` instead of `function_name('uuid')`.

Unbraced variable in string interpolation Using curly braces around variables in interpolated strings improves readability and prevents potential parsing issues. Help: Wrap the variable in curly braces, e.g., `{$variable}`.

Unbraced variable in string interpolation Using curly braces around variables in interpolated strings improves readability and prevents potential parsing issues. Help: Wrap the variable in curly braces, e.g., `{$variable}`.

Unbraced variable in string interpolation Using curly braces around variables in interpolated strings improves readability and prevents potential parsing issues. Help: Wrap the variable in curly braces, e.g., `{$variable}`.

Unbraced variable in string interpolation Using curly braces around variables in interpolated strings improves readability and prevents potential parsing issues. Help: Wrap the variable in curly braces, e.g., `{$variable}`.