Handle T_ENCAPSED_WHITESPACE as StringLiteral #393
Conversation
This file contains 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
dantleech
added a commit
to phpactor/tolerant-php-parser
that referenced
this pull request
Jan 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently the parser interprets the "node" at the offset indicated by
<>below as aSourceFileNode(orCompoundStatementNode):This is because the token is a
T_ENCAPSED_WHITESPACEtoken.I would expect this to be a
StringLiteral.This PR changes the behavior to return a
StringLiteralin this case.I've made this a draft as not entirely sure if this is the correct behavior (I think it is) or if there are other places for it to be fixed. In the meantime I will be using a fork with Phpactor.