-
Notifications
You must be signed in to change notification settings - Fork 26
Add symfony/http-foundation 6 support #16
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
base: master
Are you sure you want to change the base?
Conversation
|
Is there a reason why the Version sould be updated ? |
|
Our current project is using Laravel 9 which requires version 6 of that package. I wantet to write an jtl connector but composer can't install it because of the old version. |
|
ok, we will run some test and approve this if there are no problems |
|
Unfortunaly, the Symfony HTTP Foundation package is not the only problem. Some Laravel 9 dependecies require version 2 of the PSR Container package, but the PHP-DI package only supports version 1. There is an unreleased version of the PHP-DI package, which supports version 2 of the PSR Container package. The release should take place in the next few days. We should wait until the official release. I have tested the Connector with the DEV branch of the PHP-DI package and I had to change one line to be compatible with this version. But after that, everything seems to work correctly. |
|
Sounds good. |
|
But we have two problems with the new version of PHP-DI:
@Platzke-jtl Were the annotations used at all? Or why was |
|
@c-gross If you want, you can test with my forked package. Add this to your composer.json: And then as usual:
|
|
@zaxxo Annotations are used in the shopware6 and shopify connectors who depend on the core, but they are not directly used in core, as far as i know. While there shouln't be a problem updating http-foundation, PHP-DI would be more of a problem as we still need PHP 7 support for other connectors (at least till end of this year, probably longer) It may be possible to create a dual version, with some composer tricks. |
|
@Platzke-jtl I think the most reliable solution is to create a new connector core version 6, because of the (big) change in the PHP-DI (annotations -> attributes). So the Shopware and Shopify connector can use the old version 5, while newly created connectors can use version 6. |
Yes it's possible to install the fork via composer. |
|
After taking a deeper look at the core connector and the example connector code I'm not sure if it makes even sense to implement it inside our laravel project. Looks more like the connector is better be written as an standalone project. Like basis like the db config, not possible to use laravel config values or the .env file. Everywhere are specific config objects require. You can't just set a config param. It wants it's own models for objects like products and might not work with laravel objects as well. |
|
@c-gross Yesterday I successfully implemented the connector in our Laravel project. It was a little bit tricky, but it works. Maybe I can give you some hints or an example if you are interested in? |
|
@Platzke-jtl Is it an option to create a new connector core version 6? I could make a pull request for that. |
|
@zaxxo you can create a pr with the changes. |
|
@zaxxo ya sure and if it's to tricky I can still go the standalone way. Have a very limited time for the jtl connector. |
|
Hey guys, i have the same problem as you. And would offer my help if there is some help needed. |
Do you happen to have an example on hand for JTL running within laravel? |
|
Any update on this, @Platzke-jtl? Without |
|
@Platzke-jtl Is there any update? I would like to integrate this into a Laravel 12 project, which already needs http-foundation v7 |
No description provided.