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
I run into this issue frequently, where Psalm will throw an ArgumentTypeCoercion error for example, and then list the shape of the expected and the provided object, in a stream of about 20 lines of text, where I can't even figure out where the "parent type" text begins.
It's essentially saying "something's wrong", but won't tell you what. Any chance we can get the exact mismatch that caused the error? It doesn't have to be a complete analysis of how the two objects don't match, just the first issue it encountered and generated the issue.
As it is, I have to spend a lot of time in a text editor, analyzing the error, removing properties that are the same, and on occasion ending up with a blank file, because to me, all properties seemed to match.
Sometimes, the provided shapes contain type aliases, so you can't even compare the shape of those aliases directly. You have to track them down, and then wonder whether you ran into a bug, or you missed something.
Any help in this regard would be greatly appreciated!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I run into this issue frequently, where Psalm will throw an ArgumentTypeCoercion error for example, and then list the shape of the expected and the provided object, in a stream of about 20 lines of text, where I can't even figure out where the "parent type" text begins.
It's essentially saying "something's wrong", but won't tell you what. Any chance we can get the exact mismatch that caused the error? It doesn't have to be a complete analysis of how the two objects don't match, just the first issue it encountered and generated the issue.
As it is, I have to spend a lot of time in a text editor, analyzing the error, removing properties that are the same, and on occasion ending up with a blank file, because to me, all properties seemed to match.
Sometimes, the provided shapes contain type aliases, so you can't even compare the shape of those aliases directly. You have to track them down, and then wonder whether you ran into a bug, or you missed something.
Any help in this regard would be greatly appreciated!
Beta Was this translation helpful? Give feedback.
All reactions