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

Prevent invalid array access #68

Merged
merged 1 commit into from
Sep 14, 2020
Merged

Prevent invalid array access #68

merged 1 commit into from
Sep 14, 2020

Conversation

Nacoma
Copy link
Contributor

@Nacoma Nacoma commented Jan 16, 2020

PHP7.4 - https://www.php.net/manual/en/migration74.incompatible.php

Trying to use values of type null, bool, int, float or resource as an
array (such as $null["key"]) will now generate a notice.

PHP7.4 - https://www.php.net/manual/en/migration74.incompatible.php

> Trying to use values of type null, bool, int, float or resource as an
array (such as $null["key"]) will now generate a notice.
@goshippo goshippo deleted a comment from Nacoma Feb 28, 2020
@anthonyholmes
Copy link

Any timeline on getting this merged?

@cylosh
Copy link

cylosh commented Apr 27, 2020

This is causing alot of notices in the logs, please merge this fix.

@jfriedr jfriedr merged commit a2edfa7 into goshippo:master Sep 14, 2020
@josephmancuso
Copy link

josephmancuso commented Oct 6, 2020

@jfriedr @goshippo any way to push a release? This is a complete breaker on PHP 7.4

ErrorException: Trying to access array offset on value of type int in file /Users/Work/programming/sites/erp/vendor/shippo/shippo-php/lib/Shippo/Util.php on line 35

@jfriedr
Copy link
Contributor

jfriedr commented Oct 6, 2020

@josephmancuso I've just packaged up a release -> https://github.com/goshippo/shippo-php-client/releases/tag/v1.4.4 let me know if this doesn't address the issue!

@josephmancuso
Copy link

@jfriedr yeah but can we get it on packagist? latest release downloads 1.4.3 still.

@jfriedr
Copy link
Contributor

jfriedr commented Oct 28, 2020

@josephmancuso apologies looks like I missed this last message. After taking a look at packagist I noticed that there was a more recent version. Note that we have a webhook to publish new versions. This most recent change was done automatically.

  • To publish a new version one must update the changelog && versionfiles
  • Create a new git tag version with an updated version number
  • Push the tag to the github repo.

image

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.

5 participants