Open kevinmallinsonflynn opened 3 years ago
Hello, the library is still maintained to make sure that it doesn't break with new versions of Angular, but I'm not actively working on it, meaning that I'm not releasing new features. There's still half a million downloads per week on npm, so I don't want to force users to switch to a new library. If you care about new features being added regularly then I encourage you to switch to something else like Transloco for example.
@kevinmallinsonflynn please refer this comment https://github.com/ngx-translate/core/issues/783#issuecomment-642983145
@ocombe still waiting for reply :)
you should create a PR to add a link+description to your repository in the readme @ajayojha
@ocombe Thanks for the prompt response. Before creating the PR, It would be great if you share your precious inputs after reviewing the comment.
it looks really great, and probably a lot of those features would be nice if integrated into ngx translate, but I don't really have the time to add new features (and more maintenance) on this library anymore unfortunately, so it is great that you took the time to do that :) I'm not going to look into your code to review it in details though, because that would take a lot of time (which I don't have), sorry If you have a precise question I can try to answer it
Thanks, @ocombe. I am not expecting the code review from your side. On the weekly basis, I can spend few hours on this project to help others or feature development/bug fixes. Please let me know how we can proceed.
Title.
I prefer
ngx-translate
to angular localization library because our apps already usengx-translate
and porting it would be time consuming (unless someone knows an automated way).Therefore, does anyone have plans to maintain this project?