angular-gettext-tools
angular-gettext-tools copied to clipboard
Tools for extracting/compiling angular-gettext strings.
### Real usage : Extract for the method `gettextCatalog.getStringForLanguage`. The text is the second argument ``` gettextCatalog.getStringForLanguage( lang, 'text' ) ``` ``` const gettextExtractor = new Extractor({ moduleMethodString: "getStringForLanguage", moduleMethodStringArgumentIndex:...
The error seems to be here: https://github.com/rubenv/angular-gettext-tools/blob/v2.2.2/lib/extract.js#L263 If I have for example: ``name is $(username)`` it will get extracted to: `name is `
When installing `angular-gettext-plugin` and `angular-gettext-tools` we get high vulnerabilities errors from using an outdated version of `lodash`. There is an open issue already [here](https://github.com/augusto-altman/angular-gettext-plugin/issues/7).
I was not getting location of parse error and inspecting `err` object (https://github.com/rubenv/angular-gettext-tools/blob/7a03fac03a1c6540cf2b2abe83849750cf58f621/lib/extract.js#L223) revealed it has `loc` attribute – holding both line and column of parse error – instead of...
If we add to WebpackAngularGettext.loader.attributes = ["titles", "placeholder"] script add in export.pot tagHtml instead of title attribute value. In addition skip export angular expressions without any text.
Allow using `markerNames` to detect string literals. Simply add a leading comment to the string that contains the `markerName` (exactly) and that string will be added to the `pot` file....
Using handlebars templates I can no longer use hbs elements within script tag like: ` obj.doSomething({{{hbsVar}}}); ` and CDATA within script ` ` since version 2.2.0. I get parsing error...
Please see https://github.com/rubenv/angular-gettext/issues/365.
A custom id mapping can be provided. Examples: // do not trim the whitespace from the string ends (the current default) 'idTransform': fn(s) { return s; } // apply html...
Since version 2.3.7, there was added TSX support. This has partially broken TS parsing, since TSX syntax is forced there. The thing I stumbled upon: ``` const something = castVar;...