-
Notifications
You must be signed in to change notification settings - Fork 18
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
PHP 7.4 support #41
Comments
Hi @oprypkhantc , There are plans to update the existing dwolla-swagger-php SDK as well as investigating writing a new one from scratch. The existing dwolla-swagger-php SDK was generated using the swagger 2.0.0 spec and came with a host of issues. Updating to openAPI 3.x would likely require updates to the swagger codegen project to work with the Dwolla API. If we decide to go down that path, we'll likely do a major version bump to this SDK. |
As I said, I was able to generate a complete Dwolla API using upstream swagger-codegen and new 3.x spec, so swagger-codegen's fork shouldn't be needed anymore. We're using a fork of this for now. Thank you for the reply. |
Does someone have a solution for this? I have other packages that require 7.4, so I am stuck between keeping 7.3 just for Dwolla, or moving to 7.4 for everyone else. |
I took a quick look through your source code and I believe I've isolated the problem. Throughout your library you guys use syntax like this for function declerations:
|
Just use our fork (or fork from it): https://github.com/tenantcloud/dwolla-swagger-php/tree/php-74 "require": {
"dwolla/dwollaswagger": "^1.100",
},
"repositories": [
{
"type": "git",
"url": "https://github.com/tenantcloud/dwolla-swagger-php"
}
], We've been using it in production for almost two months now; so far so good. |
Hey there.
In php 7.4, using array access syntax on scalars/null now emits a notice: https://github.com/Dwolla/dwolla-swagger-php/blob/master/lib/models/Customer.php#L99
I've seen Dwolla/dwolla-openapi#1 and it was able to generate the SDK using it. Is there any chance of this being updated to use it?
The text was updated successfully, but these errors were encountered: