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
The best, and very nearly only, use case for String.raw I can think of is if you’re trying to use something like Steven Levithan’s XRegExp library that accepts text with significant backslashes. Using String.raw lets you write something semantically clear rather than having to think in terms of doubling your backslashes, just like you can … Read more
You can use the extension es6-string-html Note: You need to add a comment with the language in front of the multiline string
Option 1: Interpolation We can create interpolation blocks that return an empty string, and embed the comments inside them. const fields = ` id,${ /* post id */” } message,${ /* post status/message */” } created_time, permalink_url, type `; console.log(fields); Option 2: Tagged Templates Using tagged templates we can clear the comments and reconstruct the … Read more
No, ES6 does not introduce any new number formatting functions, you will have to live with the existing .toExponential(fractionDigits), .toFixed(fractionDigits), .toPrecision(precision), .toString([radix]) and toLocaleString(…) (which has been updated to optionally support the ECMA-402 Standard, though). Template strings have nothing to do with number formatting, they just desugar to a function call (if tagged) or string … Read more
This is insane. Almost every single answer here suggest running a function runtime in order to well-format, buildtime bad-formatted text oO Am I the only one shocked by that fact, especially performance impact ??? As stated by @dandavis, the official solution, (which btw is also the historic solution for unix shell scripts), is to escape … Read more
Why are template strings not allowed as literal object keys? Template strings are expressions, not literals1. You can only use string literals (and identifiers) for property names, for everything else – that is not known to be static – you need a computed property name. Is it for performance reasons? No, that’s unlikely. It’s to … Read more
If you are using template literals only with placeholders (e.g. `Hello ${person.name}`) like in the question’s example, then the result is the same as just concatenating strings. Subjectively it looks better and is easier to read, especially for multi-line strings or strings containing both ‘ and ” since you don’t have to escape those characters … Read more
It is called Tagged Template in ES-6 more could be read about them Here, funny I found the link in the starred section of the very chat. But the relevant part of the code is below (you can basically create a filtered sort). function tag(strings, …values) { assert(strings[0] === ‘a’); assert(strings[1] === ‘b’); assert(values[0] === … Read more
In my project I’ve created something like this with ES6: String.prototype.interpolate = function(params) { const names = Object.keys(params); const vals = Object.values(params); return new Function(…names, `return \`${this}\`;`)(…vals); } const template=”Example text: ${text}”; const result = template.interpolate({ text: ‘Foo Boo’ }); console.log(result);