- This topic has 6 replies, 4 voices, and was last updated 7 years, 6 months ago by
.
-
Posts
-
After an auto-update this morning TSLint changed a number of rules. Many are should be trivial to fix such as use ‘ insteadd of “, or trailing white-space rules.
However, the right-click -> fix XXXXX in same file is broken (verified on white-space and “->’).
Not sure how I can tell which versions are being used by Webclipse. My package.json is largely updated to latest. I have deleted and re-installed node_modules.
NOTE: Code compiles and runs successfully it is simply lint errors causing headaches in debug.
Question? Is there a way to prompt for updates without automatically installing?
John,
With this release we support TSLint 5. So, if you project was previously using TSLint 5, we would run embedded TSLint 4 instead, as we weren’t supporting TSLint 5.
TSLint support should use the one you have in your node_modules folder of the project. Could you please check which one is that by examining “node_modules/tslint/package.json” file? Which version do you have specified in your package.json? If this is 5, you might want to consider moving back to version 4, which was actually used by IDE so far.
> However, the right-click -> fix XXXXX in same file is broken (verified on white-space and “->’).
Could you please provide screenshots of quick fixes, which do not work well.Best regards,
Piotr TomiakI just noticed that fix white-space works for single instance in a file bit not when there are multiple instances.
Screen shots attached for new-line and white-space.
Some quick notes.
The change from 4 to 5 (or any updates) should not impact the entire team. Any updates such as this should be part of a managed roll-out by integration on my end. This requires that update be optional and manually selected (notification if good). In this scenario one person can test the update and make any required changes before the update occurs.
Not trying to be harsh, you guys have a good tool and have been really quick with updates.
John,
Thank you for your input. You are right that such an update should not influence your entire team, however so far this is the first and only complaint on evergreen updates process. We want to force updates on our users of Webclipse, especially when all of our supported technologies move so fast and we just want to avoid user frustration and reports of problems, which are already fixed. From our experience, many users just don’t update. However, in teams where there is integrator such as you, such behavior is not welcomed and we understand that. We have to consider our options here and will surely come up with some solution.
John,
Thank you for pointing to the Quick Fix issue. I could replicate the issue at my end with TSLint 5.
I have filed it for further investigation with the dev team and they are looking into it.Apologies for inconvenience caused.
–Swapna
MyEclipse SupportJohn,
We’ve put out a prerelease of the 2017 CI 6 release, which addresses the TSLint 5.x issues you mentioned, and allows you to turn off the automatic updates through preferences. To get the pre-release build, please follow the instructions in this thread: https://www.genuitec.com/forums/topic/webclipse-angular-ide-prerelease-stream/
If you can give the prerelease a try, and let us know if it fixes your issues, that would be great.
Thanks!
