translations:extract didn't work for .ts files #551
Comments
|
It seems that https://github.com/biesbjerg/ngx-translate-extract has changed the way markers work, you now have to import a specific function from their package 😞 |
sinedied
added a commit
that referenced
this issue
Sep 1, 2020
sinedied
pushed a commit
that referenced
this issue
Sep 10, 2020
# [9.0.0](8.1.1...9.0.0) (2020-09-10) ### Bug Fixes * bump min node version to 12 ([5145294](5145294)) * double prompt issue (close [#566](#566)) ([330b174](330b174)) * downgrade stylelint due to pending bugs ([5faf55a](5faf55a)) * incorrect version of @types/jest ([889b147](889b147)) * migrate tests using async to waitForAsync ([b386534](b386534)) * remove unused modules (close [#560](#560)) ([840c033](840c033)) * translation strings extraction (close [#551](#551)) ([cc58749](cc58749)) ### Features * **deps:** update packages ([05e240a](05e240a)) * upgrade to Angular 10 ([#568](#568)) ([ce64a85](ce64a85)) ### BREAKING CHANGES * Now requires Node >= 12 dues to dependencies update.
|
🎉 This issue has been resolved in version 9.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm submitting a...
Current behavior
npm run translations:extractdidn't extract strings between
extract('Hello')from ts filesExpected behavior
Should have string Hello in
src\translations\template.jsonMinimal reproduction of the problem with instructions
Add
extract('Hello')in any ts file (component, module,...)npm run translations:extractEnvironment
The text was updated successfully, but these errors were encountered: