template-strings

Let's say we have a multiline es6 Template-String to describe e.g. some URL params for a request: const fields = ` id, message, created_time, permalink_url, type `; Is there any way to have comments inside that backtick Template-String? Like: const fields = ` // post id id, // post status/message message, // ..... created_time, permalink_url, type `; No. That syntax is valid, but will just return a string containing \n// post id\nid , rather than removing the comments and creating a string without them. If you look at §11.8.6 of the spec , you can see that the only token recognized between the

According to this esdiscuss discussion , it is possible in ECMAScript 6 to define multiline strings without having to place subsequent lines of the string at the very beginning of the line. Allen Wirfs-Brock’s post contains a code example: var a = dontIndent `This is a template string. Even though each line is indented to keep the code neat and tidy, the white space used to indent is not in the resulting string`; Could someone explain how this can be achieved? How to define this dontIndent thing in order to remove the whitespace used for indentation? This feature is implemented by defining a

This question already has an answer here: Backticks calling a function 2 answers I have a simple logging function: function log(str) { console.log('logged: ', str); } If I call it without parentheses (currently using Chrome's dev tools) and pass in a template string, like this: log`foo` The output is: logged: ["foo", raw: Array[1]] If I call it with parentheses, log(`foo`) The output is: logged: foo Why does calling a function using a template string an no parentheses work in Javascript? What is happening that causes the result to be different from calling it with parentheses? Sampson The

I have a long string, which I build using ES6 template strings, but I want it to be without line breaks: var string = `As all string substitutions in Template Strings are JavaScript expressions, we can substitute a lot more than variable names. For example, below we can use expression interpolation to embed for some readable inline math:` console.log(string); Result: As all string substitutions in Template Strings are JavaScript expressions, we can substitute a lot more than variable names. For example, below we can use expression interpolation to embed for some readable inline math: My

I have to work around the limitation of gettext to recognise ES6 template strings, and I thought about getting the "non interpolated value" of the template strings as a compilation step, in order to have only "normal" strings in the code. Basically what I would like to achieve is transform this const adjective = 'wonderful' const something = `Look, I am a ${adjective} string` console.log(something) > "Look, I am a wonderful string" into this const adjective = 'wonderful' const something = 'Look, I am a ${adjective} string' console.log(something) > "Look, I am a ${adjective} string" One brutal

I understand the syntax of ES6 tagged templates . What I don't see is the practical usability. When is it better than passing an object parameter, like the settings in jQuery's AJAX ? $.ajax('url', { /*this guy here*/ }) Right now I only see the tricky syntax but I don't see why I would need/use it. I also found that the TypeScript team chose to implement it (in 1.5) before other important features. What is the concept behind tagged string templates? You can use tagged templates to build APIs that are more expressive than regular function calls. For example, I'm working on a proof-of-concept