-
Notifications
You must be signed in to change notification settings - Fork 666
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
Convertion of partials to full imports #7155
Conversation
I guess the error is related to #7153?! |
@@ -1124,7 +1136,7 @@ public function getSymbolLocation(string $file_path, string $symbol): ?CodeLocat | |||
|
|||
$file_contents = $this->getFileContents($file_path); | |||
|
|||
return new CodeLocation\Raw( | |||
return new Raw( |
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 is an example of where readability does suffer. Could be renamed to RawLocation
though.
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.
Yep, Raw
is quite inexpressively.
The good thing is, it is used only 4 times. Anyway, DocblockTypeLocation
and ParseErrorLocation
are postfixed, so this should really be RawLocation
.
But I think this should go into an extra PR.
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.
But I think this should go into an extra PR.
Of course.
I'm halfway through the review, and this is actually not too bad. |
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.
Note to self: review ParseTree, UnresolvedConstant and CodeLocation class naming.
Those two should probably also be added to that list:
|
Thanks! |
I finally have converted "all" partial to full imports.
I was looking at all cases but I don’t think readability suffers at any case, as mostly they are unambiguous due prefixing or postfixing or just by naming or context.
One exception is the
PhpParser
namespace which will need an extra issue for discussion and so is left out here.