[Process] Fix Process::getEnv() when setEnv() hasn't been called before#45931
[Process] Fix Process::getEnv() when setEnv() hasn't been called before#45931nicolas-grekas merged 1 commit intosymfony:4.4from
Conversation
|
Hey! I see that this is your first PR. That is great! Welcome! Symfony has a contribution guide which I suggest you to read. In short:
Review the GitHub status checks of your pull request and try to solve the reported issues. If some tests are failing, try to see if they are failing because of this change. When two Symfony core team members approve this change, it will be merged and you will become an official Symfony contributor! I am going to sit back now and wait for the reviews. Cheers! Carsonbot |
nicolas-grekas
left a comment
There was a problem hiding this comment.
Good catch.
I think it might be better to initialize the property to the empty array, then we wouldn't have to patch this method.
Also, since this is a bugfix, it should target 4.4, and should have a test case. Can you add one please? (I can handle the re-targeting while merging)
|
Sorry I have heavy work on my job, so I'm afraid that I'm not available to do future works. Just fix it thought your standard way, thanks. |
|
Thanks @asika32764. |
AS
getEnv()return type is array, if aProcessobject has no default env and is NULL value, callinggetEnv()will get error.