-
Notifications
You must be signed in to change notification settings - Fork 60
Fix nested curly braces in template strings #1539
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
Draft
Copilot
wants to merge
5
commits into
master
Choose a base branch
from
copilot/fix-1538
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.
+152
−13
Draft
Changes from 2 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
c3b659d
Initial plan
Copilot ab1643f
Fix nested curly braces in template strings by tracking brace depth
Copilot 3829c16
Refactor nested brace handling to use state-based approach
Copilot 8f9a606
Merge branch 'master' into copilot/fix-1538
TwitchBronBron 87c7e14
Implement stack-based approach for nested template expressions
Copilot 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
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.
I don't like that we've essentially inlined the main loop inside template strings. this will be difficult to maintain in the future. can you find a different way to handle this where we're sharing this logic instead of inlining it? Or a different approach entirely?
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.
You're absolutely right about the maintainability concerns. I've refactored the implementation to use a state-based approach instead of inlining the scanning logic.
Changes made:
tokenKindMaptotokenFunctionMapwith logic to check template expression stateisInTemplateExpressionandtemplateExpressionBraceDepthinstance variablestemplateStringmethod to use existingscanTokenlogic instead of custom loopThis approach reuses all existing scanning logic, eliminating code duplication and making it much more maintainable. All tests continue to pass.
Commit: 3829c16
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.
That's pretty creative. However, what about nested template expressions? This only supports a max depth of one. But we could have stuff like this:
Please update the logic to handle this more complicated situation while still keeping it maintainable and reusable.
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.
I've implemented a stack-based approach to handle nested template expressions. The solution uses a
templateExpressionStackto track multiple levels of nesting, with each entry containing the brace depth for that template expression level.The implementation:
tokenKindMaptotokenFunctionMapwith logic to check template expression state\one${two${three${four}`}`}``The approach is partially working but I'm still debugging an issue where template string quasi processing is capturing
}characters that should be processed asTemplateStringExpressionEndtokens. The stack correctly tracks nesting levels, but the boundary between template string parsing and template expression parsing in nested contexts needs refinement.Commit: 87c7e14