Skip to content

[PropertyInfo] ensure compatibility with type resolver 0.5 #33626

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

Merged
merged 1 commit into from
Sep 18, 2019

Conversation

xabbuh
Copy link
Member

@xabbuh xabbuh commented Sep 18, 2019

Q A
Branch? 3.4
Bug fix? yes
New feature? no
Deprecations? no
Tickets
License MIT
Doc PR

same as #33588 but for the 3.4 branch


if ($nestedVarType instanceof Nullable) {
$varTypes[] = (string) $nestedVarType->getActualType();
$nullable = true;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it expected that this could never be false again the loop? Just asking, I am currently on a phone 😊

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At least that's the current behaviour. The failing example docblock here was ?string|int which was expected to reveal string and int as types both being nullable.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the thing is, nullable applies to the whole typehint. Either null is allowed or it is not. But it cannot be both of them.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @stof, that’s what I thought but wanted to be sure 👍🏻

@fabpot
Copy link
Member

fabpot commented Sep 18, 2019

Thank you @xabbuh.

fabpot added a commit that referenced this pull request Sep 18, 2019
… (xabbuh)

This PR was merged into the 3.4 branch.

Discussion
----------

[PropertyInfo] ensure compatibility with type resolver 0.5

| Q             | A
| ------------- | ---
| Branch?       | 3.4
| Bug fix?      | yes
| New feature?  | no
| Deprecations? | no
| Tickets       |
| License       | MIT
| Doc PR        |

same as #33588 but for the `3.4` branch

Commits
-------

2d708b3 ensure compatibility with type resolver 0.5
@fabpot fabpot merged commit 2d708b3 into symfony:3.4 Sep 18, 2019
@xabbuh xabbuh deleted the type-resolver-compat branch September 18, 2019 15:30
This was referenced Oct 7, 2019
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.

5 participants