You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment we can only specify custom parameters in the XML config. I propose we also allow specifying the same on the command line. Of course, the naive solution presents a problem where extensions may register names that conflict with (future) PHPUnit parameters, but I propose all such extension parameters be double-prefixed: first with a global extension prefix (x) and then with a custom prefix they register themselves.
For example, my printer, Pip, may register the pip prefix and then it can be passed command-line arguments in the form:
--x-pip-my-param='my value'
The extension registering the pip prefix will receive all command-line arguments so prefixed with --x-pip- automatically.
The text was updated successfully, but these errors were encountered:
At the moment we can only specify custom parameters in the XML config. I propose we also allow specifying the same on the command line. Of course, the naive solution presents a problem where extensions may register names that conflict with (future) PHPUnit parameters, but I propose all such extension parameters be double-prefixed: first with a global extension prefix (
x
) and then with a custom prefix they register themselves.For example, my printer, Pip, may register the
pip
prefix and then it can be passed command-line arguments in the form:--x-pip-my-param='my value'
The extension registering the
pip
prefix will receive all command-line arguments so prefixed with--x-pip-
automatically.The text was updated successfully, but these errors were encountered: