facebook

Pipe resolution not working with typescript 2.2.x

  1. CodeMix & Angular IDE
  2.  > 
  3. Webclipse 1.x Help
Viewing 15 posts - 1 through 15 (of 24 total)
  • Author
    Posts
  • #519042 Reply

    Daniel
    Participant

    Hi

    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.png

    Attachments:
    You must be logged in to view attached files.
    #519131 Reply

    support-swapna
    Moderator

    Daniel,

    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 Support

    #519229 Reply

    Daniel
    Participant

    Thank you very much Swapna.

    #521754 Reply

    Brian
    Participant

    Is there any update for this issue? I have been seeing these errors for the past month.

    #521934 Reply

    support-swapna
    Moderator

    Brian,

    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 Support

    #522004 Reply

    support-swapna
    Moderator

    Daniel/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 Support

    #522107 Reply

    Jan
    Participant

    Had the same issue, can confirm it has been fixed in CL5.

    Thanks guys/girls. 😉

    #522231 Reply

    support-swapna
    Moderator

    Jan,

    Thank you for getting back to us. Glad that it works.
    Please let us know if you see any issues.

    –Swapna
    MyEclipse Support

    #524344 Reply

    Sten
    Participant

    Hello,

    i still see the “Unable to resolve signature for pipe invocation” marker. (see screenshot)
    The update options says “no updates for webclipse found”

    best
    Sten

    Attachments:
    You must be logged in to view attached files.
    #524346 Reply

    Jan
    Participant

    @Sten,

    did 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
    Jan

    #524347 Reply

    Sten
    Participant

    Thx 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.

    #524348 Reply

    Jan
    Participant

    Hm 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
    Jan

    #524349 Reply

    support-piotr
    Participant

    Sten,

    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 6 years, 11 months ago by support-piotr.
    • This reply was modified 6 years, 11 months ago by support-piotr.
    #524352 Reply

    Jan
    Participant

    Sure 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 🙂

    #524356 Reply

    Sten
    Participant

    braking it down to almost nothing using a built in pipe…. see files attached

    • This reply was modified 6 years, 11 months ago by Sten.
    Attachments:
    You must be logged in to view attached files.
Viewing 15 posts - 1 through 15 (of 24 total)
Reply To: Pipe resolution not working with typescript 2.2.x

You must be logged in to post in the forum log in