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
An actual example is vendor/bin/psalm --init script 1
There's no --level flag. [level=3] would be clearer. Including the value of the level in the error message would make it clearer that level= shouldn't be part of the CLI invocation. (Or mentioning an example invocation)
Another possible approach would be to a --level/--init-level flag? If more flags for init get added, providing an un-named list would get unwieldly.
As an example, a user might want to provide multiple source directories?
The current help text:
-i, --init [source_dir=src] [--level=3]
Create a psalm config file in the current directory that points to [source_dir]
at the required level, from 1, most strict, to 6, most permissive
The text was updated successfully, but these errors were encountered:
An actual example is
vendor/bin/psalm --init script 1
There's no
--level
flag.[level=3]
would be clearer. Including the value of the level in the error message would make it clearer thatlevel=
shouldn't be part of the CLI invocation. (Or mentioning an example invocation)--level
/--init-level
flag? If more flags for init get added, providing an un-named list would get unwieldly.The current help text:
The text was updated successfully, but these errors were encountered: