Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[PropertyInfo] Dont try to set null when argument is not nullable#38920

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Closed
Nyholm wants to merge3 commits intosymfony:5.2fromNyholm:propertyInfo-nullable

Conversation

@Nyholm
Copy link
Member

@NyholmNyholm commentedOct 31, 2020
edited by nicolas-grekas
Loading

QA
Branch?5.3
Bug fix?yes
New feature?no
Deprecations?no
TicketsPart of#38800
LicenseMIT
Doc PR

This will break up#38800 into two smaller pieces.

If there is a methodsetPreviousException(Throwable $t) and we try to unserialise a value of ['previousException'=>null], we should not try to invoke this setter. It will cause an error.

@Nyholm
Copy link
MemberAuthor

The testtestThrowTypeErrorWithNullArgument is failing for this. Why would the desired behavior be that we get an Error likeExpected argument of type "Throwable", "null" given?

@jderusse
Copy link
Member

If it's a bug fix, shouldn't it target 4.4?

Copy link
Member

@jderussejderusse left a comment

Choose a reason for hiding this comment

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

What's about constructor, non nullable properties (typehinted in php 7.4) and mutators?.

@Nyholm
Copy link
MemberAuthor

If it's a bug fix, shouldn't it target 4.4?

Last time I checked, the code was very different in 4.4 and 5.1. I can check again later.

@nicolas-grekasnicolas-grekas added this to the5.2 milestoneNov 2, 2020
@fabpot
Copy link
Member

@Nyholm Can you finish this one? I think it should go in 5.2.

@fabpotfabpot modified the milestones:5.2,5.xNov 30, 2020
@NyholmNyholm changed the base branch from5.x to5.2February 15, 2021 16:07
Copy link
Member

@nicolas-grekasnicolas-grekas left a comment

Choose a reason for hiding this comment

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

Can you please rebase to target 5.3?

@nicolas-grekasnicolas-grekas modified the milestones:5.4,5.3Sep 8, 2021
@fabpot
Copy link
Member

@Nyholm What's the status here?

@fabpot
Copy link
Member

@Nyholm Sorry to ping you again on this one :)

@Nyholm
Copy link
MemberAuthor

I thought i would patch a simple bug. But Im not sure this is needed. I dont even remember what I did to find this bug. Im closing this since it has not been a priority for me (or anyone else) to fix it.

@NyholmNyholm closed thisJul 25, 2022
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@nicolas-grekasnicolas-grekasnicolas-grekas left review comments

@jderussejderussejderusse left review comments

@xabbuhxabbuhxabbuh left review comments

@dunglasdunglasAwaiting requested review from dunglasdunglas is a code owner

Assignees

No one assigned

Projects

None yet

Milestone

5.3

Development

Successfully merging this pull request may close these issues.

6 participants

@Nyholm@jderusse@fabpot@nicolas-grekas@xabbuh@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp