GNU gettext - Bugs: bug #62203, JavaScript parser stops at the 1st...
You are not allowed to post comments on this tracker with your current authentication level.
bug #62203: JavaScript parser stops at the 1st template string in curly braces ”{}“ after left shift operators ”<<“
Submitter: | tuberry | ||
Submitted: | Sat 19 Mar 2022 07:11:24 PM UTC | ||
Category: | JavaScript | Severity: | 3 - Normal |
Item Group: | None | Status: | None |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Open |
Fri 10 Feb 2023 06:03:15 PM UTC, comment #1: |
Gianni Lerro <glerro> |
Sat 19 Mar 2022 07:11:24 PM UTC, original submission:
As the title,
|
tuberry |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
No changes have been made to this item
I have a similar problem, i don't have a "<<" but a "++".
In my case JavaScript parser stops at the 1st template string in curly braces ”{}“ after increment operators ”++“.
```js
// test.js
if (this._nAttempts++ < 100) {
_('a');
{
_('b')
`${1}`;
_('c');
}
_('d');
```
Only string `a` and `b` will be extracted when running `xgettext test.js --output=-` in a terminal. (gettext 0.21-11 / Debian Testing)