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
It would be great if there was a second-level error message (a refinement of the previous error message), which described which properties are a mismatch, including Expected and Actual types.
Describe alternatives you've considered
Only show the differences. While less visually "noisy", this may reduce utility for some users, who may want the full Expected and Actual types.
Additional context
Prior art can be seen in TypeScript error messages, which show multiple levels of error messaging, with each becoming more specific than the last:
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When encountering a long SafeQL error, it's not easy to quickly and visually see the differences which are causing the mismatch:
Describe the solution you'd like
It would be great if there was a second-level error message (a refinement of the previous error message), which described which properties are a mismatch, including Expected and Actual types.
Describe alternatives you've considered
Only show the differences. While less visually "noisy", this may reduce utility for some users, who may want the full Expected and Actual types.
Additional context
Prior art can be seen in TypeScript error messages, which show multiple levels of error messaging, with each becoming more specific than the last:
The text was updated successfully, but these errors were encountered: