-
-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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 5.x reaches the end of life by the end of 2018 #1246
Comments
cc @jebentier (2017/07) @dkarlovi (2017/07) @mandrean (2017/08) @jfastnacht (2017/09) @ackintosh (2017/09) @ybelenko (2018/07) |
There are worthwhile challenges ✨:
|
I'm working on PHP Slim refactoring descripted in #426. In short it's separating generated stubs from user implementation. I'm quite sure that it will be breaking changes without fallback, so maybe we should include both migration to 7.0.x and interfaces/implementation refactoring to the next release? @ackintosh @wing328 Does it sounds right to you? Should I address both PRs to 4.0.0? |
Thanks for your great work. It sounds good to me. 👍 |
The php README still says "Requirements: PHP 5.5 and later" |
@jacobweber good catch. Do you mind filing a PR to update it (template)? |
So this issue is still out there. Any hopes of addressing it soon? 5 is long gone by now. I tried using the phpLegacySupport options, but it seems to do nothing when using the php generator, despite actually producing more strongly typed code when using the php-symfony generator (see this) EDIT: see #5480 |
Current progress of migration to PHP 7.x:
|
Description
PHP 5.x reaches the end of life by the end of 2018 so we need to upgrade our PHP clients, servers to use PHP 7.x as the default.
Ref: http://php.net/supported-versions.php
openapi-generator version
I suggest we do it as part of the 4.0.0 release (next major release)
Suggest a fix/enhancement
If anyone wants to help on this, please reply to let us know.
The text was updated successfully, but these errors were encountered: