-
Notifications
You must be signed in to change notification settings - Fork 125
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
Update php parser to v5 #802
base: next
Are you sure you want to change the base?
Conversation
Hey @vdauchy ! Thanks for contributing ! If you have any issues please ask I'll be glad to help 😃 |
9632b3b
to
f5ab626
Compare
f5ab626
to
bdcefa2
Compare
Hi @Korbeil ! Thanks for answering, I updated everything to be compatible with the latest 4.x and ^5.0.
If you have some idea for the styling I'm interested :-) |
Quick follow up:
The only solution I see for the formatting issue with php-parser v5 is to add CS-Fixer as dev-depedency to composer and enable Any thoughts ? I don't see any addition to do to this PR (but the styling following your advise), so let's me know if you need anything else to move forward :-) |
Interestingly, this closes #760 |
Hi!
This is bigger than expected... it's basically just the update to PHP-Parser 5 (changelog: https://github.com/nikic/PHP-Parser/blob/master/UPGRADE-5.0.md) as I had conflicts with other dev dependencies.
There is a few changes(in the first commit) which change a lot of generated code (second commit).
For PHP-Parser the only added feature (kind of...) is the option
php-version
which target the parser and is used like this:Most of the changes on the generated code are styles (
function foo() : Bar
changed tofunction foo(): Bar
) and the use ofFoo\Bar::class
instead ofFoo\\Bar
string.Now I need to try this out directly on my own projects using my fork, let me know what you think :-)