With editableSearchTerm=true, ng-select is not visually cleared when model value is cleared (or updated)

[earshinov]

Describe the bug

With an <ng-select [editableSearchTerm]="true"> bound to a model value via [(ngModel)] or [formControl], ng-select is not cleared when the model value is cleared (set to null) or changed.

This is an intentional duplicate of #1971, which has been closed as stale.

Reproducible example
https://stackblitz.com/edit/angular-ivy-qsdnki (also contains repro steps)

Expected behavior
See also the example linked above.

1. formControl.setValue(null) should clear ngSelect.searchText and ng-select's visual representation
2. modelValue = null should also clear ngSelect.searchText and ng-select's visual representation

Screenshots
A screenshot of the example page linked above:

Environment

• Windows 10 (actually does not matter)
• Microsoft Edge 108.0.1462.54 (actually does not matter)
• ng-select 10.0.1 (latest)

Additional context
Related issues:

• The field is not cleared when the control is updated with editableSearchTerm #1971

[Tomal991]

Anyone?? Is this bug/issue solvable??

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions 🎆

[earshinov]

Bumping to remove the "stale" mark. The bug is still there.

[mgohin]

Got the problem too, very very annoying :/

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions 🎆

[earshinov]

Here is some activity: I believe the issue is still present

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions 🎆

[earshinov]

I don't think this issue was fixed.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions 🎆

[earshinov]

Still not fixed

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions 🎆

[earshinov]

☝️

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions 🎆

[earshinov]

☝️

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions 🎆

[earshinov]

Bumping once again

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions 🎆

[earshinov]

☝️