-
-
Notifications
You must be signed in to change notification settings - Fork 351
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
[Traverser] Refactor BetterNodeFinder::findFirstNext() to remove next attribute usage #3879
Conversation
b237f29
to
f205c56
Compare
cce4f12
to
702cef5
Compare
It seems cause error infinite loop, I will check more :) |
// todo: use +1 key once all next node attribute reference and NodeConnectingVisitor removed | ||
// left with add SlimNodeConnectingVisitor for only lookup parent | ||
return $node->getAttribute(AttributeKey::NEXT_NODE); |
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.
@TomasVotruba @staabm I tried many things, and it keep crashing/infinite loop without this one left over.
I think this part can be removed once we have all next/prev node attribute removed and removed the NodeConnectingVisitor, left with add SlimNodeConnectingVisitor for only lookup parent
All checks have passed 🎉 @TomasVotruba I think it is good enough for now 👍 |
@TomasVotruba I am merging it for now, in separate PR, i will try improve |
@TomasVotruba @staabm this is continue of PR:
to remove next attribute usage on
BetterNodeFinder::findFirstNext()
Ref rectorphp/rector#7940