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

Merge 3.1.x up into 4.0.x #11304

Merged
merged 8 commits into from
Feb 25, 2024
Merged

Merge 3.1.x up into 4.0.x #11304

merged 8 commits into from
Feb 25, 2024

Conversation

greg0ire
Copy link
Member

No description provided.

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.
Remove wrong annotation about return type
Merge 2.18.x up into 3.0.x
Merge 3.0.x up into 3.1.x
The phpdoc comment for the return type of
ClassMetadata::fullyQualifiedClassName() says that the return type will
be null if the input value is null. I have made it more precise by
using "if and only if", made the null check more strict and translated
that into template annotations. Also, since we say we return a
class-string, I've asserted that.
It can easily be avoided by the only caller.
Translate comment into code and annotations
@greg0ire greg0ire merged commit 7679fc0 into 4.0.x Feb 25, 2024
128 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant