Skip to content

dart editor: does not colorize text correctly in multi-line comments with embedded ${} #1003

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

Closed
DartBot opened this issue Dec 29, 2011 · 1 comment
Assignees

Comments

@DartBot
Copy link

DartBot commented Dec 29, 2011

This issue was originally filed by [email protected]


Open attached file in Dart Editor

Expected:File is syntax highlighted correctly.
Actual: Text after the ${} feature is not highlighted correctly.


Attachment:
bug.dart (161 Bytes)

@bwilkerson
Copy link
Member

This has already been fixed, and the fix should be available in the next build.


Set owner to @bwilkerson.
Added Fixed label.

dart-bot pushed a commit that referenced this issue Mar 17, 2021
2021-03-17 [email protected] Fixes #1017. Use => for setter returning value tests
2021-03-16 [email protected] Issue #996: more tests for Generic functions as type arguments and bounds added.
2021-03-16 [email protected] Fixes #1005. Description updated for method_definition tests
2021-03-16 [email protected] Fixes #1011. Expect an error if non-function type is called as a function
2021-03-16 [email protected] Issue #996: tests for Generic functions as type arguments and bounds re-factored, more tests added.
2021-03-15 [email protected] Issue #996: tests for Generic functions as type arguments and bounds added.
2021-03-15 [email protected] Issue #996: tests for Generic functions as type arguments and bounds added.
2021-03-15 [email protected] Missed experiment flag added
2021-03-12 [email protected] Issue #996: tests for Generic functions as type arguments and bounds added.
2021-03-12 [email protected] #993. Added tests checking that Struct fields cannot have initializers
2021-03-12 [email protected] #993. Tests for not external members of Struct subtype added
2021-03-11 [email protected] #993. Use package ffi in co19 ffi tests
2021-03-09 [email protected] Fixes #995. Annotations with type arguments tests added
2021-03-09 [email protected] Issue #997: existing triple-shift tests corrected.
2021-03-09 [email protected] More fixes for #535: split constant evaluation tests because static behavior of the strong and weak mode is different.
2021-03-04 [email protected] #993. Array tests added
2021-03-04 [email protected] #993. Pointer equality tests added
2021-03-03 [email protected] #993. Pointer.elementAt() tests added
2021-03-02 [email protected] #993. Pointer.cast() tests added
2021-03-01 [email protected] #993. Pointer tests added
2021-03-01 [email protected] Fixes #936. Change expected result according to the new left top rule
2021-02-26 [email protected] Fixed #998: tests checks output streams correctly now.
2021-02-26 [email protected] #993. IntPtr tests added
2021-02-26 [email protected] #993. More Struct tests added
2021-02-25 [email protected] Tests updated, missing issue tags added.
2021-02-25 [email protected] #1003. Isolate test fixed to not to be a racy
2021-02-25 [email protected] Issue numbers added
2021-02-24 [email protected] Issue number added
2021-02-24 [email protected] #988. Typo in error message fixed
2021-02-24 [email protected] #988. Fix test expectations

Cq-Include-Trybots: dart/try:analyzer-nnbd-linux-release-try,dart2js-nnbd-linux-x64-chrome-try,ddc-nnbd-linux-release-chrome-try,front-end-nnbd-linux-release-x64-try,vm-kernel-nnbd-linux-debug-x64-try,vm-kernel-nnbd-linux-release-simarm64-try,vm-kernel-nnbd-linux-release-x64-try,vm-kernel-nnbd-mac-release-x64-try,vm-kernel-nnbd-win-release-x64-try,vm-kernel-precomp-nnbd-linux-debug-x64-try,vm-kernel-precomp-nnbd-linux-release-simarm64-try,vm-kernel-precomp-nnbd-linux-release-x64-try
Change-Id: I718644028b1d2a9fbba0c7efdf2923bb67184fde
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/191409
Reviewed-by: William Hesse <[email protected]>
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants