adding documentation about @no-named-arguments and allowNamedArgumentCalls #5654
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I saw a change on a project today where allowNamedArgumentCalls was set to false. I expected this to have the same effect as a
@no-named-argument
project-wide but it didn't seem to work.After thinking about that, my assumption didn't make sense because without
@no-named-argument
directly in code, Psalm can't enforce the absence of named parameters on external calls.Those were largely undocumented so I added some details