Additional spaces in pipe when use angular parser

Prettier 2.7.2 [Playground link](https://prettier.io/playground/#N4Igxg9gdgLgprEAuEAeGBXAlgWgDZZRw5gAWAhgE4wA6UABI-QFRQDmAYhJQLw0h44MemSrCIAM3oATcgE8AzvzpMRecgoV9wFasoZMA2qThY2pGAF1tAJgAMd-asMB3LNJilr-NkIDq7p4AFJTk7HAAlE5GAG7keBhw3jpi9AA+9JhYHFh48JT0SPQSufmF9KHh6ZnYALLkAA4NcAVFMBAAchgAtgBGLQrllb76AHyoAPRZ+ITEotSjdCAANCAQDTBY0ArIoFSUEC4AClQIOyjxLvI7q72hYADWQgDK5N1wADKzyBLxCnC3e5PGDPBrkMCENjIGCURKrOB9ODSaRIj5hNgYci+LiUbrkGCbdjIEDkDDtFYgCzdPB+UhYeAKMFgODPM70rAxelyYlgTQUwj-ahHUJsPE-P4AkAAKwUAA9npDBABFDAQeDivD-VZgyiC4nojDqSgUhqUQgwAIeUjIACM9m1B3+flCDWJprggpicApAEdVfBhetziSFDgiEikRTKHA-Vho8KsWKkL9NZL-t0sNDYWnFXAVWrvcmJasYORepbPMgbCXQrlIQBhCDdJMgD0AVgpGH+ABUy+cU1qQDFEgBJKAo2DPMBmjYAQXHzxgckEGv+AF810A)

# Options (if any):
--parser angular

Input:

<tui-line-chart
    *ngFor="let chart of days"
    class="chart"
    [height]="200"
    [width]="getWidth(range)"
    [value]="chart | tuiFilter : filter : range | tuiMapper : toNumbers : range"
></tui-line-chart>

Output:

<tui-line-chart
  *ngFor="let chart of days"
  class="chart"
  [height]="200"
  [width]="getWidth(range)"
  [value]="chart | tuiFilter: filter:range | tuiMapper: toNumbers:range"
></tui-line-chart>

Expected behavior:

I feel it’s much better to read with spaces.

    [value]="chart | tuiFilter : filter : range | tuiMapper : toNumbers : range"

[waterplea]

I asked a friend of mine, GDE for Angular, for his opinion. He said, “I haven’t seen much discussion about the format of this syntax, and it’s hard to decide”. Sorry we are going to close this issue for now. But it does not mean that we as Prettier will never accept your proposal. If several similar issues are opened in the future, we can consider them again.

I’m a GDE for Angular too 🙂 I’ve asked @splincode to raise this issue when he enabled Angular as template parser for prettier in our huge open source library Taiga UI and we all were confused by how weird it looks without spaces 🙂

[nseni]

@sosukesuzuki It’s a shame this issue was not discussed more thoroughly. Opinions of a few Taiga UI users should not overweight all the examples in the official Angular documentation, where pipes are separated with spaces, and pipe arguments stand close to pipe names:

{{ (user$ | async).credit | currency:'CAD':'symbol-narrow':'4.2-2' }}

not

{{ (user$ | async).credit | currency : 'CAD' : 'symbol-narrow' : '4.2-2' }}