Tagged: Pipe, Typescript 2.2.x
- This topic has 23 replies, 7 voices, and was last updated 8 years, 1 month ago by
Sten.
-
AuthorPosts
-
DanielParticipantHi
After updating to Typescript 2.2.2, all HTML templates using a pipe show an error marker. This applies to both, built-in and custom pipes, respectively.
@Typescript 2.2.x
When using a pipe the editor complains with the following error:Unable to resolve signature for pipe invocation.
[1]
Also, when hitting the F3 key to open the pipe’s definition, an internal error is raised. [2]@Typescript 2.1.6
Pipe resolution works as expected, meaning no error in the problems view and the pipe declaration can be opened.Best Regards,
Daniel
—-
[1] screenshot-1.png
[2] screenshot-2.pngAttachments:
You must be logged in to view attached files.April 10, 2017 at 7:31 am #519131
support-swapnaModeratorDaniel,
Thank you for raising this issue. I could replicate it at my end. I have filed a bug for the dev team and they are looking into it. We will keep you posted about the fix schedule.
Apologies for inconvenience caused.
–Swapna
MyEclipse SupportApril 10, 2017 at 3:36 pm #519229
DanielParticipantThank you very much Swapna.
May 5, 2017 at 11:47 am #521754
BrianParticipantIs there any update for this issue? I have been seeing these errors for the past month.
May 8, 2017 at 4:41 am #521934
support-swapnaModeratorBrian,
The fix will be out with our next update to Webclipse 2017 CI which is due for release today.We will keep you posted when the release is out.
Sorry for inconvenience caused.
–Swapna
MyEclipse SupportMay 8, 2017 at 2:10 pm #522004
support-swapnaModeratorDaniel/Brian,
Webclipse 2017 CI 5 is out. Please update to CI 5 from menu Help > Webclipse > Check for Updates and let us know if you see any issues.
–Swapna
MyEclipse SupportMay 9, 2017 at 6:11 am #522107
JanParticipantHad the same issue, can confirm it has been fixed in CL5.
Thanks guys/girls. 😉
May 9, 2017 at 11:28 pm #522231
support-swapnaModeratorJan,
Thank you for getting back to us. Glad that it works.
Please let us know if you see any issues.–Swapna
MyEclipse SupportMay 26, 2017 at 6:49 am #524344
StenParticipantHello,
i still see the “Unable to resolve signature for pipe invocation” marker. (see screenshot)
The update options says “no updates for webclipse found”best
StenAttachments:
You must be logged in to view attached files.May 26, 2017 at 6:53 am #524346
JanParticipantdid you do a Project – Clean after updating Webclipse?
This helped for me. Also make sure your Pipe is actually accessable / runnable by running an NG serve ignoring the error shown. -> does this work for you?Regards
JanMay 26, 2017 at 7:05 am #524347
StenParticipantThx Jan,
yes I tried to clean the project(s)! That did not help.
All my pipes are working as expected when testing with ng serve.
It is just an eclipse/webclipse problem.May 26, 2017 at 7:09 am #524348
JanParticipantHm ok, to bad 🙁
This is how I created my pipe, maybe you spot a difference there, even if your pipe works?
Maybe we can narrow down the parsing issue.@Pipe({ name: 'slackemoji' }) export class SlackemojiPipe implements PipeTransform {...}
registered using a provider:
providers: [SlackemojiPipe],
Cheers
JanMay 26, 2017 at 7:20 am #524349
support-piotrParticipantSten,
Can you provide full code of the pipe excluding method bodies? And please share the template part where you use the pipe. It looks like there is some typing issue in your definition.
Best regards,
Piotr Tomiak-
This reply was modified 8 years, 1 month ago by
support-piotr.
-
This reply was modified 8 years, 1 month ago by
support-piotr.
May 26, 2017 at 7:28 am #524352
JanParticipantSure here you go, for me the pipe issue has been fixed however:
import { Pipe, PipeTransform } from '@angular/core'; import { DomSanitizer } from '@angular/platform-browser'; @Pipe({ name: 'slackemoji' }) export class SlackemojiPipe implements PipeTransform { constructor(private _sanitizer: DomSanitizer) { } transform(value: any, args: any[] = []) { return this._sanitizer.bypassSecurityTrustHtml(value); } escapeRegExp(str) { } replaceURLWithHTMLLinks(text) { } replaceMailToReference(text) { } replaceSlackReference(text) { } }
@Component({ selector: 'xxx', templateUrl: './question.component.html', styleUrls: ['./question.component.css'], providers: [SlackemojiPipe], })
using the pipe:
<div class="card card-block bg-faded qna-box"> <div class="message-container" [innerHTML]="wsElement.content.content | slackemoji"></div> </div>
Happy hunting 🙂
May 26, 2017 at 7:37 am #524356 -
This reply was modified 8 years, 1 month ago by
-
AuthorPosts