You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have Angular 11 project. I've been using transloco-keys-mahager 2.6.0 for a while.
And faced with problem that was solved in 3.0.2.
I updated to latest (3.2.0).
Used FIND
And got:
TypeError: Cannot destructure property 'name' of 'e.variables.find(...)' as it is undefined.
at resolveMetadata (/home/vladimir/Projects/neos-ng-sorm-ui/node_modules/@ngneat/transloco-keys-manager/keys-builder/template/structural-directive.extractor.js:1:1833)
at traverse (/home/vladimir/Projects/neos-ng-sorm-ui/node_modules/@ngneat/transloco-keys-manager/keys-builder/template/structural-directive.extractor.js:1:599)
at structuralDirectiveExtractor (/home/vladimir/Projects/neos-ng-sorm-ui/node_modules/@ngneat/transloco-keys-manager/keys-builder/template/structural-directive.extractor.js:1:290)
at templateExtractor (/home/vladimir/Projects/neos-ng-sorm-ui/node_modules/@ngneat/transloco-keys-manager/keys-builder/template/index.js:1:967)
at inlineTemplateExtractor (/home/vladimir/Projects/neos-ng-sorm-ui/node_modules/@ngneat/transloco-keys-manager/keys-builder/typescript/inline-template.js:1:462)
at TSExtractor (/home/vladimir/Projects/neos-ng-sorm-ui/node_modules/@ngneat/transloco-keys-manager/keys-builder/typescript/index.js:1:1512)
at extractKeys (/home/vladimir/Projects/neos-ng-sorm-ui/node_modules/@ngneat/transloco-keys-manager/keys-builder/utils/extract-keys.js:1:1011)
at extractTSKeys (/home/vladimir/Projects/neos-ng-sorm-ui/node_modules/@ngneat/transloco-keys-manager/keys-builder/typescript/index.js:1:721)
at buildKeys (/home/vladimir/Projects/neos-ng-sorm-ui/node_modules/@ngneat/transloco-keys-manager/keys-builder/build-keys.js:1:364)
at findMissingKeys (/home/vladimir/Projects/neos-ng-sorm-ui/node_modules/@ngneat/transloco-keys-manager/keys-detective/index.js:1:867)
I checked versions from 3.0.0 to 3.2.0. All of them gave me this error.
Checked version 2.7.5. No error.
I found "@angular/compiler": "12.2.6" dependency in your package.json in versions 3.0.0+. And maybe it's related some how, because of my 11 version....
Expected behavior
transloco-keys-mahager 3+ version works in Angular 11 project
And maybe does not depend on Angular major version
Please provide a link to a minimal reproduction of the bug
@Alegiter The reason that in v3, the keys manager depends on the Angular compiler is because of implementation changes within the library make it more stable by using AST instead of regexes which were hard to maintain.
You are welcome to investigate the issue and open a PR fix (if possible), but if you can't use the v3+, you are welcome to use v2+ until you upgrade to Angular v12+.
Of course, if this issue still occurs on Angular v12+, feel free to reopen 🙂
Is there an existing issue for this?
Is this a regression?
No
Current behavior
I have Angular 11 project. I've been using transloco-keys-mahager 2.6.0 for a while.
And faced with problem that was solved in 3.0.2.
I updated to latest (3.2.0).
Used FIND
And got:
I checked versions from 3.0.0 to 3.2.0. All of them gave me this error.
Checked version 2.7.5. No error.
I found "@angular/compiler": "12.2.6" dependency in your package.json in versions 3.0.0+. And maybe it's related some how, because of my 11 version....
Expected behavior
transloco-keys-mahager 3+ version works in Angular 11 project
And maybe does not depend on Angular major version
Please provide a link to a minimal reproduction of the bug
Can't prove a link
Transloco Config
Debug Logs
Please provide the environment you discovered this bug in
Additional context
No response
I would like to make a pull request for this bug
No
The text was updated successfully, but these errors were encountered: