-
[PR 2599](https://github.com/facebook/reason/pull/2599) implements string template literals in a way that is a non-breaking change with Reason Syntax 3.6.
It is good to go as is, but there's a coup…
-
### Installed product versions
- Visual Studio: 2017 Community
- This extension: 2.4.340
### Description
Error parsing source with template literal tags
### Steps to recreate
1. Create a *.j…
-
As mentioned in #3452, a Webpack-specific version of the template literals transformers would allow compressing `css` and `html` tagged template literals in bundles. This would be a good addition for …
-
Sometimes I have code in a string:
```js
const js = `
const msg = 'this doesnt have any language server features';
console.log(msg);
`
```
There is a vscode extension that allows syntax…
-
This is just a suggestion. If it sounds good, let me know. I'd love to be able to create my first pull request here.
### The case
I see that composing a string from my data is something that is …
-
This is not an issue with this project, but rather than an Apps Script issue.
Long story short, if you are using template literals, and they contain symbols for comments, google will strip these at t…
-
**Is your feature request related to a problem? Please describe.**
Strings inside template literals are currently not obfuscated.
For example:
```js
console.log(`Hello World`)
```
Will prese…
-
| Sequence | Name | {N} |
| -------- | ----------------- | --------------------- |
| `\x{N}` | hexadecimal value | 32 digits >= 1 digits |
| | | |
The hex escape …
-
**Describe the bug**
We are working to adopt `eslint-plugin-lingui` and most rules are fine, however `lingui/text-restrictions` is pretty much unusable.
Our source code contains a lot of templat…
Bertg updated
2 months ago
-
### What steps will reproduce the problem?
The Japanese prompt is not displayed at all. Cut-offs are occurring. But English prompt is displayed perfectly.
( It's may be occured with some multi…