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

Sylius 1.13 #496

Closed
wants to merge 33 commits into from
Closed

Sylius 1.13 #496

wants to merge 33 commits into from

Conversation

Prometee
Copy link
Contributor

@Prometee Prometee commented May 13, 2024

Q A
Bug fix? no
New feature? no
BC breaks? no
Deprecations? no
Related tickets fixes #495
License MIT

Since Sylius 1.13 is requiring PHP >= 8.1 this plugin have to be a little bit updated.
This PR aim to support it and also update, cleanup and re-standardize some configs files.

List bellow, the changes made to the plugin.

Globally

  • Remove Sylius 1.11 support.
  • Cleanup .gitignore files.

Test application

  • Use Symfony runtime.
  • Update package.json with the latest version from sylius/sylius-standard.
  • Cleanup Kernel.php
  • Strange bug with Sylius 1.12, I fixed.yml file not loading because it needs to have .yaml extension.

Tests

  • Update Behat config to use symfony/panther.
  • Update Behat ChromeDriver reference to PantherDriver.
  • Update PHPStan config (and remove outdated bitbag/coding-standard config import).
  • Rename PHPStan neon config to phpstan.neon.dist (FYI: it allows to set an extra config into a developer env).
  • Fix PHPSpec issue with TwigFunction being final.
  • Update ECS config and avoid checking var and node_modules folders.
  • Fix the Behat image uploader on Setup\PageContext to avoid uploading image outside of the dedicated folder.

@SzymonKostrubiec
Copy link
Contributor

Hi,
I made some fixes to a copy of your branch and then deployed a new PR.
Details here:
#498

@SzymonKostrubiec
Copy link
Contributor

Support for sylius 1.13 has been added #498

@Prometee
Copy link
Contributor Author

@SzymonKostrubiec is there a reason on why you start a new PR instead of simply clone my repository branch and commit to it ? Or maybe you don't know it's something possible on GitHub ?

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.

Sylius 1.13 support
2 participants