-
-
Notifications
You must be signed in to change notification settings - Fork 6
Upgrade nikic/php-parser
to v5+
#63
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
Open
BrianHenryIE
wants to merge
8
commits into
voku:master
Choose a base branch
from
BrianHenryIE:upgrade-phpparser-5
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
2392fd8
Mute `command not found: nproc`
BrianHenryIE 5836d87
Determine number of cores on macOS
BrianHenryIE 846e011
`composer require "nikic/php-parser":"^5"`
BrianHenryIE 6f1542f
Add `test-coverage` Composer script
BrianHenryIE c55dc7a
Instantiate parser via `::createForNewestSupportedVersion()`
BrianHenryIE 63113e2
`composer require "nikic/php-parser":"^4.18 || ^5"`
BrianHenryIE 9356c18
Check `method_exists` for deprecated `::getParts()`
BrianHenryIE a436917
Replace deprecated `Node::getLine()` with `Node::getStartLine()`
BrianHenryIE File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change correctly adapts for
php-parser
v5 by checking forgetParts()
. However, the fallback: $node->value->name->name
for the v5 path might not be robust for all cases, especially for fully qualified names.PHP-Parser v5 Name Handling: For
php-parser
v5,PhpParser\Node\Name
objects (includingFullyQualified
,Relative
, etc.) provide atoString()
method for reliable string conversion. Using$node->value->name->name
can be problematic because:new \My\Namespace\MyClass()
), thename
property might not exist on theFullyQualified
object, or it might only contain the last part of the name, not the full FQN.$node->value->name->toString()
is the recommended way to get the complete string representation of anyName
node in v5.Original Elvis Operator: It appears the original Elvis operator
?: $node->value->name->name
(which was part ofimplode(...) ?: $node->value->name->name
) has been removed from the v4 path in this PR (thetrue
branch of the ternary). Ifimplode('\\', $node->value->name->getParts())
results in an empty string, the behavior for the v4 path will now differ from the original code. Was this change in behavior for the v4 path intentional?For the v5 path, could we use
$node->value->name->toString()
for more reliable name resolution? This would align better with thephp-parser
v5 API.