Skip to content

Conversation

@RickKukiela
Copy link

This addresses the possible bug still present in 2.0.3 which I discussed in this issue post:

#458

…is used as the 3rd parameter of a `preg_replace()` call. This call can and will return `NULL` in some circumstances, and passing a non-string value there will result in, at best, a deprecated error being thrown.
@gnongsie
Copy link
Contributor

Hi @RickKukiela,

Thank you for this PR.

Unfortunately, absorbing this change and releasing it will take some time. Kindly be patient with us.

-- Gabriel

@RickKukiela
Copy link
Author

All good! Thanks for confirming receipt :)

gnongsie added a commit that referenced this pull request Sep 2, 2024
@gnongsie
Copy link
Contributor

gnongsie commented Sep 2, 2024

Closing this PR as the fix has been added as part of a different commit.
Also, I am not using type casting, in the event that it causes issues later on.
Instead, I will check for null and provide an empty string if the object is null.

@gnongsie gnongsie closed this Sep 2, 2024
alex-galkin-hostaway pushed a commit to Hostaway/sdk-php that referenced this pull request Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants