Replies: 2 comments
-
This would also fix #355 |
Beta Was this translation helpful? Give feedback.
-
This is not an easy-switch ... It implies that we have to rewrite the complete code generation part from scratch and deal with nikic/php-parser specific issues while working our way through it. One of the questions I ask myself: what value do we actually gain from doing this massive destructive switch? I rather spend that time working on some more blocking issues inside this package like advanced metadata parsing and improved code generation on additional XSD information. The numbers of downloads you provide might also not reflect reality for various reasons:
Sure there might have been some breaking changes between v3 and v4, meaning we have to change stuff in this repo. Are there any specific reasons why you want to switch code-generating package? |
Beta Was this translation helpful? Give feedback.
-
Feature Request
Currently, Soap Client uses Laminas Code to generate code with
generate
commands. What do you think about switching it to Nikic PHP-Parser?There are several benefits but the main one is that PHP-Parser is used by many many more libraries (according to Github it's 922k vs 90k) like PHPStan and others and thanks to that all the newest features are usually supported really fast.
Summary
Beta Was this translation helpful? Give feedback.
All reactions