These are tagged template literals. The part before the backpacks is a reference to a function that will be called to process the string. The function is passed the variables (the ${} parts) as arguments as well as the pieces of the string that surround the variables broken into an array. The return value of … Read more
The only case where $ does not produce the literal $ is before a {, otherwise you do not need to escape it. var response = `You have $${money}` does work therefore. In case you need to escape anything, the backslash \ is the escape character in template strings as well, so (while unnecessary) the … Read more
Yes, it’s possible, but you had for some reason put the )}) part (that closes the require call, the interpolated value, and the CSS url) in the wrong place: { background: `url(${require(`../../assets/${edge.node.name.toLowerCase()}.png`)}) center no-repeat` // ^^^ } That said, it’s probably a bad idea as it doesn’t exactly make the code readable. Better use a … Read more
Two answers for this problem, but only one may be considered optimal. Inside template literals, javascript can be used inside of expressions like ${}. Its therefore possible to have indented multiline template literals such as the following. The caveat is some valid js character or value must be present in the expression, such as an … Read more
You can go with formatted string literals (“f-strings”) since Python 3.6 f”Hi {name}, you are {age}” Or string formatting “Hi {}, you are {}”.format(name, age) “Hi {name}, you are {age}”.format(name=name, age=age) Or format specifiers “Hi %s, you are %d” % (name, age)
If you look at the ECMAScript 6 compatibility table, you’ll see that template literals are not supported by IE11. The “use strict”; statement doesn’t really change anything, because before it is determined whether a code is in strict mode, it has to be parsed first, but it can’t be parsed, because you’re using syntax that the … Read more
Code-wise, there is no specific disadvantage. JS engines are smart enough to not have performance differences between a string literal and a template literal without variables. In fact, I might even argue that it is good to always use template literals: You can already use single quotes or double quotes to make strings. Choosing which … Read more
If you insert </script> inside a script tag, no matter if it’s a string in quotes, apostrophes, or even a template literal, it will always close the script tag. You have to escape it, for example like that: var str=` <script> <\/script> ` var pre = document.createElement(‘pre’) pre.textContent = str document.body.appendChild(pre) However, if you use … Read more
2020 answer: there is still nothing built into the JS stdlib to handle de-denting long lines, although TC39 has discussed adding a new template literal that handles indentation. You have 2 options presently: The endent and dedent-js packages will handle this. Note the dedent-js package actually works with both tabs and spaces. var dedent = … Read more
ES6 Template literals (Template strings) cannot be used inside an Angular component input, because the Angular compiler doesn’t know this grammar. The way that you provided is fine. <app-my-component [myInput]=”‘My name is ‘ + name + ‘!'”></app-my-component> Or something like this, In the component, // In the component, you can use ES6 template literal name: … Read more