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
Add explicit braced property access parsing #260
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
c0227c2
fix: braced property access
wyozi 4bb5a68
Test quoted property access tokenizing
wyozi df3f088
Test getVariableAsText
wyozi c06dbf9
Add incomplete quoted property access test
wyozi 4113363
Make end brace peek stricter and fix the test
wyozi 6744905
Test for broken quoted property access
wyozi File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
import * as chai from 'chai' | ||
import * as sinonChai from 'sinon-chai' | ||
import { PropertyAccessToken } from '../../../src/tokens/property-access-token' | ||
import { QuotedToken } from '../../../src/tokens/quoted-token' | ||
import { WordToken } from '../../../src/tokens/word-token' | ||
|
||
chai.use(sinonChai) | ||
const expect = chai.expect | ||
|
||
describe('PropertyAccessToken', function () { | ||
describe('getVariableAsText', function () { | ||
it('should return correct value for WordToken', function () { | ||
const token = new PropertyAccessToken(new WordToken('foo', 0, 3), [], 3) | ||
expect(token.getVariableAsText()).to.equal('foo') | ||
}) | ||
it('should return correct value for QuotedToken', function () { | ||
const token = new PropertyAccessToken(new QuotedToken('"foo bar"', 0, 9), [], 9) | ||
expect(token.getVariableAsText()).to.equal('foo bar') | ||
}) | ||
}) | ||
}) |
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.
How about
["foo"]["bar"]
or["foo"].bar
?We need adapt the following logic (the
PropertyAccessToken
part) to support this case (remove thevariable
constructor argument and make it the first props maybe?).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.
Makes sense, although the number of potential valid syntaxes are getting a bit scary. Do you think that could be postponed into the future and this feature shipped as is (once I fix the tests passing)?
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.
Seems it can be done by consume the
[
, call readValue recursively(as in props brackets), and consume the]
. This way the following cases will be supported also: