Skip to content

[Bug] - TXJS File Parser incorrectly parses text on certain occasions #197

Open
@mark-hopper

Description

@mark-hopper

Current Behavior
The text which is pushed to Transifex via the CDS contains all the attributes (such as count, id, link, text)

Expected Behavior
The text pushed to Transifex via the CDS contains only the data passed to the translate pipe (e.g. 'Security')

Steps to Reproduce
Produce a html template which contains the following code snippet
<ng-container *ngIf="!data.equipment.manual && alertSettings.enableSecurity"> <ng-container *ngTemplateOutlet="el; context: { count: data.security?.length, id: 'assetpage-actionstab-securitytab-button', link: ['/fleet', data.equipment.id, 'actions', 'security'], text: ('Security' | translate:{ _key: 'text.asset_details.tab.security', _tags: 'asset_details' }), }"></ng-container> </ng-container>

Use the TXJS push mechanic to parse the file and look at the end outcome which is pushed to Transifex.

Possible Solution
My suspicions here, is that the brackets on the "text" property have potentially thrown the parser - Either that or the use of the ngTemplateOutlet in this manner.

Possible Implementation
Not obligatory, but suggest an idea for implementing addition or change

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions