August 30, 2017 at 8:36 am #535212
Thank you for the log file. The dev team is looking into the problem.
They will get back to you soon.
Apologies for inconvenience caused.
MyEclipse SupportSeptember 4, 2017 at 3:16 pm #535491
We haven’t been able to specifically reproduce this problem, but we have fixed a number of bugs that might be the cause. Would it be possible for you to upgrade to a pre-release of CI 8 to see if it fixes the issues you are experiencing with your project? If not, I will send you some debugging settings which you can add to the IDE as our final resort.
Instructions on how to upgrade to the pre-release are here: https://www.genuitec.com/forums/topic/webclipse-angular-ide-prerelease-stream/December 7, 2017 at 7:24 am #544649
Any news about this? It’s still not working…December 7, 2017 at 12:43 pm #544674
Sorry to hear you are still experiencing this issue – since we hadn’t heard from you after my last post, we assumed the 2017 CI 8 update fixed your problem.
1) Have you updated to CI 9 if not, can you please do so?
2) Can you send us a screenshot of your project properties > TypeScript page?
3) Please attach the workspace error log. You can find it at
[workspace_location]/.metadata/.logJanuary 10, 2018 at 10:15 am #547675
I am using the latest version. But still not checks/assists for HTML template files. Perhaps a problem with the NG language service?
I attached all the necessary files.
Attachments:You must be logged in to view attached files.January 24, 2018 at 3:01 am #549123
Any news on this? Still a little annoying to have bought a product that does not work as promised on my project.January 24, 2018 at 4:50 am #549137
I’m terribly sorry we missed your previous post. In the set of screenshots you last shared, the TypeScript property page shows
tsconfig.jsonselected – it should in fact be
tsconfig.app.jsonas we had discussed previously.
Could you change it to ensure it has the right file selected and then restart the IDE just to be absolutely sure this change is being picked up (this is typically not required, but I want to rule out all variables). Check now if you are getting the content assist and validation you expect. If it still isn’t working, we can get into a video call and try to figure this out live.January 25, 2018 at 7:40 am #549237
Don’t know why it is on the screenshot – but I verified (and also tried again to re-import project): And both times it was configured correctly to “tsconfig.app.json”. Still not working.January 25, 2018 at 2:11 pm #549247
Understood. When would be a good time to have a call so we can take a look at this first hand? Sometime tomorrow or on Monday perhaps.January 29, 2018 at 3:33 am #549622
Wednesday between 10:00UTC+1 and 17:00UTC+1 ?January 29, 2018 at 6:02 am #549629
Wednesday 11:00 AM UTC+1 sounds good. I’ll send you a private message with the meeting details.January 31, 2018 at 4:13 am #550051
I waited for about 10 minutes on the call today, but you did not join. Did you receive the private message with the meeting details I sent on Monday?
When would you like to reschedule this call?February 1, 2018 at 7:31 am #550182
Found the reason for this: It seems that the “node-modules” folder must be visible in the navigator to be recognized as Angular project. This can be checked via project settings – Typescript: Anuglar must be listed there with a version. I filtered it out via project settings – “Resource/Resource Filters”. No everything works as expected.February 1, 2018 at 12:38 pm #550221
Thank you for taking the time to meet with us today and posting back here – we’re glad we figured out the problem. Though the node_modules issue was certainly one of the problems, we found another issue with how some versions in the package.json are being parsed – which is why it wasn’t picking up the version from there either.
We’re going to try and pick up the fix for the version parsing as well as the keybindings issue you mentioned in the CI 11 release – should be out in the next week or so.
You must be logged in to reply to this topic.