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 know for ngx-extractor command, input should be TS files, something like (-i "./src/**/*.ts"), but this will pick up text with i18n property from source folder files only. But how about the files in packaged node module projects which has i18n property of outside template?
So, can't ngx-extractor generate translations for entire repository/project (including node module projects) ? or is there any other tool alternative to ngx-extractor?
I see that for official i18n (HTML's) it picks up even the child projects under node modules, and generates translations referring to "component.d.ts".
@ocombe need your help on this
I know for ngx-extractor command, input should be TS files, something like (-i "./src/**/*.ts"), but this will pick up text with i18n property from source folder files only. But how about the files in packaged node module projects which has i18n property of outside template?
So, can't ngx-extractor generate translations for entire repository/project (including node module projects) ? or is there any other tool alternative to ngx-extractor?
I see that for official i18n (HTML's) it picks up even the child projects under node modules, and generates translations referring to "component.d.ts".
The text was updated successfully, but these errors were encountered: