Change tippy content dynamically if tippy content is already shown up

[ArgV04]

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Performance issue
[x] Feature request
[ ] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:

Current behavior

Expected behavior

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Hey, is it possible to change the tippy content dynamically during the tippy content is already shown?

Environment

Angular version: 12.xx


Browser:
- [] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
 
For Tooling issues:
- Node version: XX  
- Platform:  

Others:

[NetanelBasal]

What's the use case?

[ArgV04]

The use case is using tippy for showing validation errors in mat-form-field when multiple validators triggering errors while the user is entering something into an input field for example. The first validation error is shown with tippy normally, but if the validation error message changes the already shown message content does not change when an other validation error got's higher priority to shown up.

So here is a quick example how we configured tippy for showing up. The getErrorTranslationId() ,method is fetching us the corresponding error message translation ID.

<mat-form-field [isVisible]="formControl.invalid && formControl.touched" tippy="{{getErrorTranslationId() | transloco}}" trigger="manual"> <input formControlName="formControl" matInput> </mat-form-field>

[NetanelBasal]

You can use ng-template and change the content inside it.

[NetanelBasal]

We can also expose setContent method for your case. I don't mind seeing a PR.

[ArgV04]

ng-template is working neither :/ the showing up tippy content does not gets updated

[ArgV04]

alright, I solved my problem by using ng-templates ;) Thanks for the hint