grunt-angular-translate

grunt-angular-translate copied to clipboard

Hi! I'm trying to extract from ``` {{entity.id}} ``` If a use a custom regex, I can get what I need (SEARCH.SAMPLES.ID) The problem is that **{{entity.id}}** is also extracted....

fidjetunnafcillin

GitHub changed the way Markdown headings are parsed, so this change fixes it. See [bryant1410/readmesfix](https://github.com/bryant1410/readmesfix) for more information. Tackles bryant1410/readmesfix#1

bryant1410

Ternary operator parsing produces some false results

2

With the patch from PR #69 the code snippet below will generate both the false translation keys `active` and `non-active` in addition to the correct one `STATE_LABEL`. ``` HTML 3...

phw

Changed HtmlFilterTernary regex to fix problem with ternary operations between two translations. Please check the test to have a better idea of the problem.

jivasquez

I have the following call to `$translate` in my app that isn't picked up by grunt-angular-translate: ``` $translate(['LOGIN.RECOVERY.FORM.MESSAGES.SUCCESS', 'LOGIN.CREATE_NEW_PASSWORD.FORM.BUTTONS.CONFIRM'], {email: vm.email}) ``` This is because the RegEx for matching these...

rgant

Support the translate-namespace directive

3

Namespaces are supported by grunt-angular-translate, but not the https://angular-translate.github.io/docs/#/api/pascalprecht.translate.directive:translateNamespace directive. The `translate-namespace` directive allows a developer to avoid repeating the namespace in a view by extracting it to a parent...

sgilroy

If I have the data-translate attribute in my template and use single quotes instead of double quotes, it is not picked up by the extractor. Using double quotes works as...

mrhaasguy

Create one file per component.

7

With angular 2 going the component oriented approach to building applications I would like to have the possibility to extract translation keys per component so I end up with a...

reppners

customRegex as object

2

Hi, I saw at master that I can use an object for customRegex. I was happy, because I searched a way to add prefix to some translation keys: ``` $stateProvider.state(...

Ulrikop

Incorrect parsing for interpolation in a directive

1

There is incorrect parsing in the case of interpolating the translation ID inside a directive. The following line is pulled into the language file like so: File.jade: ``` span(translate="{{$ctrl.cardData.comparisonString}}") {{$ctrl.cardData.comparisonString}}...

stefan2718