You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Noel Abrahams (@NoelAbrahams) I understand that. This is probably a lousy experience for most people, and as the one who implemented templates, I personally felt like I owed our users something a little better. This afternoon I whipped something up.
I have a branch from which you can build the source code and swap out your language service in VS2013. The specific commit (e42ce9c) can be cherry picked onto the release-1.4 branch.
Basically, as long as your template strings' substitutions don't contain:
Expressions with closing curly braces on a separate line
Other substitution template strings that span multiple lines
this should fit your needs.
If it doesn't, well, you probably have other problems to worry about. 😉
Daniel Rosenwasser (@DanielRosenwasser), will try that out. Do you mean to say that in VS 2015 this should be coloured correctly? (A bug in NTVS is preventing us from using VS 2015 atm, but we should be migrating soon.)
Activity
DanielRosenwasser commentedon Jan 16, 2015
Duplicate of #1477, see my comment for an explanation of the technical difficulties associated with this: #1477 (comment) .
Though, we could enhance the lexical classifier, but I don't know if it's really worth it.
NoelAbrahams commentedon Jan 19, 2015
Daniel Rosenwasser (@DanielRosenwasser), colour would really help
The template string version is more difficult to comprehend.
DanielRosenwasser commentedon Jan 20, 2015
Noel Abrahams (@NoelAbrahams) I understand that. This is probably a lousy experience for most people, and as the one who implemented templates, I personally felt like I owed our users something a little better. This afternoon I whipped something up.
I have a branch from which you can build the source code and swap out your language service in VS2013. The specific commit (e42ce9c) can be cherry picked onto the
release-1.4branch.Basically, as long as your template strings' substitutions don't contain:
this should fit your needs.
If it doesn't, well, you probably have other problems to worry about. 😉
NoelAbrahams commentedon Jan 20, 2015
Daniel Rosenwasser (@DanielRosenwasser), will try that out. Do you mean to say that in VS 2015 this should be coloured correctly? (A bug in NTVS is preventing us from using VS 2015 atm, but we should be migrating soon.)
Thanks!
DanielRosenwasser commentedon Jan 20, 2015
You're very welcome! Let me know how this works out for you. Yes, 2015 should already work with template colorization.
That's unfortunate - does the Node Tools team know about the bug?
NoelAbrahams commentedon Jan 21, 2015
Yes, there's a discussion item.
DanielRosenwasser commentedon Feb 13, 2015
A fix is now in
masterthrough #2026.