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

Supports Symfony ^7.0 #476

Closed
wants to merge 1 commit into from
Closed

Supports Symfony ^7.0 #476

wants to merge 1 commit into from

Conversation

tentacode
Copy link

@tentacode tentacode commented Apr 9, 2024

Change Log

Added

  • Support for Symfony 7.0

Fixed

Changed

Removed

Deprecated

Security


Description

Hello 👋 thanks for phpmatcher ! I'm using it extensively on all my projects ! I could not install it on a Symfony 7.0 project so here is the bump of composer. Feel free to tell me if there something else needed or if you prefer to do it yourself. Meanwhile I'll be using my fork.

@tentacode
Copy link
Author

tentacode commented Apr 9, 2024

Looks like it's still a work in progress, I have an issue with Doctrine/Lexer.

Doctrine/Lexer ^3.0 breaks the code and needs refactoring.

@tentacode tentacode force-pushed the symfony7 branch 2 times, most recently from 2e6e9ba to 852abd8 Compare April 9, 2024 12:31
@norberttech
Copy link
Member

hey @tentacode I'm glad that php matcher is useful for you 😊
About the upgrade, lexer is a known problem, it was already mentioned in #473 and #475

I believe that long term solution should be to move away from doctrine/lexer and replace it with phplrt however as a quick fix, I'm fine with reducing support just to lexer ^3.0 - this might help you fix those broken tests.

@@ -21,15 +21,15 @@
"ext-simplexml": "*",
"aeon-php/calendar": "^1.0",
"coduo/php-to-string": "^3",
"doctrine/lexer": "^1.0||^2.0"
"doctrine/lexer": "^1.0||^2.0||^3.0"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as already mentioned, I would simplify it by allowing only "^3.0"

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, but as I'm on doctrine orm 3.0 I'm forced to use lexer 3 😅 I'll keep the fork because it's "workish" and I can use it in my project, but i'll remove merge request in your repository, good luck with the fix ! (if ever I have the time I'll look into it)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm but if you remove 1 and 2, it should work for you and I could merge it, no?

Copy link
Author

@tentacode tentacode Apr 11, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah sorry I haven't read your message properly, lexer 3.0 has a lot of BC Break and the code of phpmatcher don't work with it :(

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, I once tried to upgrade to 3.0 but it wasn't working and I didn't had then enough time to debug why but it seems that it wasn't a bug on my end but rather some changes in the internal behavior of lexer.
I'm gonna close this PR since it can't be merged anyway, sorry

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.

2 participants