Closed BorntraegerMarc closed 7 years ago
@tflori could you please publish a new version, once this is resolved? :)
my suggestion is to change the failing tests / tslint config from travis. Because for most of the users the tslint will fail because they use the default one from angular...
I'm fine with changing the tslint configuration. So if build works I can release a new version..
Sent from my OnePlus ONEPLUS A3003 using FastHub
@tflori One test still fails but I don't really know why. Could you help me out?
I don't understand why you changed TranslateParams but not tslint.json...
Is it necessary to have the @input declaration in front of the setters now?
I think the biggest problem will be the setting no-eval
because without this the Translator.parse()
method will throw an error. I think the problem is located in ng cli that does not exclude node_modules directory...
If you find a way without failing tests it would be great. I'm currently working on other projects and can't really help on this minor issue (from my point of view).
Is the only problem the selector of translate? Try moving the Input specification to @Component specification again. Maybe this helps.
I'm still wondering if ng lint checks the code of angular-translator?
Sent from my OnePlus ONEPLUS A3003 using FastHub
Thanks for the feedback. Changing the tslint.json wouldn't help because projects using the translator would have their own tslint.json and would override it. This is my source for tslint exclude not working: https://github.com/palantir/tslint/issues/73
Based on this doc, it seems like a bad practice: https://angular.io/guide/styleguide#style-05-03
But I figured out now that the files actually can be excluded from the angular config directly. So we don't need the tsconfig. I adapted this now and it works: https://github.com/mgechev/codelyzer/issues/268#issuecomment-298395031
Closing this PR although I recommend to adapt the project to the style guidelines at some point...
To fix (angular's default) tslint errors. These errors should definitely be fixed, because with tslint it is currently not possible to exclude folders when running
ng lint
. So these tslint errors cause our CI build to fail...These were the errors: