[support-piotr]

Jan,

Sorry, but I should have asked Sten to provide his pipe data. In your case everything works, right?

[Jan]

@support-piotr
Yes, for me your new release fixed the bug.
Also it looks like @Sten is not providing a provider – if he is using global pipes:
providers: [SlackemojiPipe]

Best
Jan

[support-piotr]

@Jan,

In such a case it would validate with error that the pipe cannot be provided, so that has to do something with signature of the method.

[Sten]

@support-piotr

did you see my post #524356?

I do see the red marker even if I try to use a simple built in pipe like ‘uppercase’.

import { Component } from ‘@angular/core’;

@Component({
selector: ‘test’,
template: ‘<h1>{{\’hello world\’ | uppercase}}</h1>’,
styles: [”]
})
export class TestComponent{
}

The pipes are working properly when running the whole application.

• This reply was modified 7 years, 5 months ago by Sten.

[support-piotr]

Sten,

Sorry, missed that reply. I can’t reproduce the issue locally, could you please share your package.json?

Best regards,
Piotr Tomiak

[Sten]

yes (tried different versions… this is the last one):

{
“name”: “something”,
“version”: “0.1.0”,
“license”: “MIT”,
“angular-cli”: {},
“scripts”: {
“ng”: “ng”,
“start”: “ng serve”,
“test”: “ng test”,
“pree2e”: “webdriver-manager update –standalone false –gecko false”,
“e2e”: “protractor”
},
“private”: true,
“dependencies”: {
“@angular/common”: “^2.3.1”,
“@angular/compiler”: “^2.3.1”,
“@angular/core”: “^2.3.1”,
“@angular/forms”: “^2.3.1”,
“@angular/http”: “^2.3.1”,
“@angular/platform-browser”: “^2.3.1”,
“@angular/platform-browser-dynamic”: “^2.3.1”,
“@angular/router”: “^3.3.1”,
“@ng-bootstrap/ng-bootstrap”: “^1.0.0-alpha.21”,
“angular2-font-awesome”: “^1.1.0”,
“angular2-google-maps”: “^0.17.0”,
“bootstrap”: “^4.0.0-alpha.6”,
“core-js”: “^2.4.1”,
“font-awesome”: “^4.7.0”,
“ng2-file-upload”: “^1.2.0”,
“ng2-img-fallback”: “^0.2.2”,
“rxjs”: “^5.0.1”,
“ts-helpers”: “^1.1.1”,
“zone.js”: “^0.7.8”
},
“devDependencies”: {
“@angular/compiler-cli”: “^2.3.1”,
“@types/jasmine”: “2.5.38”,
“@types/node”: “^6.0.42”,
“angular-cli”: “1.0.0-beta.28.3”,
“angular-ide”: “^0.9.16”,
“codelyzer”: “~2.0.0-beta.1”,
“jasmine-core”: “2.5.2”,
“jasmine-spec-reporter”: “2.5.0”,
“karma”: “1.2.0”,
“karma-chrome-launcher”: “^2.0.0”,
“karma-cli”: “^1.0.1”,
“karma-jasmine”: “^1.0.2”,
“karma-remap-istanbul”: “^0.2.1”,
“protractor”: “~5.1.0”,
“ts-helpers”: “^1.1.2”,
“ts-node”: “2.0.0”,
“tslint”: “^4.5.0”,
“typescript”: “~2.2.0”
}
}

[support-piotr]

Sten,

I’ve reproduced the issue with your package.json. Looks like it’s specific to Angular 2. We will try to fix it ASAP.

Best regards,
Piotr Tomiak

[Brian Fernandes]

We’ve put out a prerelease of the 2017 CI 6 release, which addresses these issues. To get the pre-release build, please follow the instructions on this thread: https://www.genuitec.com/forums/topic/webclipse-angular-ide-prerelease-stream/

Do let us know if your issue is fixed by the prerelease stream, so we can ensure the final 2017 CI 6 release correctly addresses your problems.

[Sten]

Yess!!

prerelease of the 2017 CI 6 fixed the issue in my case!

I just had to follow the linked instruction and clean the project.
All red markers are gone now.

Great support!!
thank you

• This reply was modified 7 years, 5 months ago by Sten.

[Author]

Posts