-
-
Notifications
You must be signed in to change notification settings - Fork 394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
abort_if not treated like if statements by type checker #116
Comments
Well, first, this is a very weird error message that shouldn't happen: But to the original issue, Larastan should contain these two things: *
|
On I've whipped up a repository that reproduces the error, before reading your reply fully, anyway if it's ever needed keryja/larastan-error-examples#reproduce-abort-if.
|
They don't. The type there must be something else, not MixedType. |
@keryja This issue still exists on the latest version? |
--level
used: maxDescription:
Currently
abort_if
does not seem to get treated similarly to if, anything designated as nullable is still considered nullable afterabort_if
This results in an error when querying relations on the object:
Workaround/example:
Current workaround for this is to use an if statement with a regular
abort
:The text was updated successfully, but these errors were encountered: