add ", but" for InvalidArgument error message where a type is provided #8364
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.
Added a "but" after the "," in InvalidArgument errors, so one can easily find where the provided type starts. If the function has a param with array{} with many parameters and nested array{}, it is often very hard to find where the expected type ends and the provided type starts.
This is a very simple example, in reality I often had cases with 25+ keys.
https://psalm.dev/r/2e6a506272