Skip to content
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

Remove wrong annotation about return type #11293

Merged
merged 1 commit into from
Feb 24, 2024

Conversation

greg0ire
Copy link
Member

@greg0ire greg0ire commented Feb 22, 2024

Found while working on #11294

Although this method is guaranteed to return either null or something that can be used as a fully qualified class name, it never actually checks that the class actually exists. Adding such a check breaks several tests, including some that expect a exceptions at some later points in the execution.

Although this method is guaranteed to return either null or something
that can be used as a fully qualified class name, it never actually
checks that the class actually exists. Adding such a check breaks
several tests, including some that expect a exceptions at some later
points in the execution.
@greg0ire greg0ire marked this pull request as draft February 24, 2024 10:57
@greg0ire
Copy link
Member Author

@greg0ire greg0ire marked this pull request as ready for review February 24, 2024 12:04
@greg0ire
Copy link
Member Author

Second thoughts dissipated by @ondrejmirtes himself :)

@greg0ire greg0ire merged commit 76c4539 into doctrine:2.18.x Feb 24, 2024
58 checks passed
@greg0ire greg0ire deleted the wrong-type branch February 24, 2024 12:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants