-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TreeSelect: Issue with TreeSelect in PrimeNG 16 - Unwanted '0' Prefix in Labels #14285
Comments
I opened same issue few weeks ago, no feedback till now |
A workaround for this issue is to create a template to override the label. Unfortunatelly there is no predefined template to do this. So you have to set the property https://stackblitz.com/edit/skfymg-giimzn Note: In PrimeNG 17 this problem no longer exists |
@jschu PrimeNG 17, not an option for now, it require Angular 17, which require Node 18. |
this seems like a specific problem with the template |
Hi, This issue is already fixed and cannot be replicated with the latest version. Could you please share a stackblitz example if it still exists? |
Hi, |
Not working in my case with the same primeNG version. The templating doesn't work at all |
I still see these counter at the end! |
Hi, So sorry for the delayed response! Improvements have been made to many components recently, both in terms of performance and enhancement. Therefore, this improvement may have been developed in another issue ticket without realizing it. You can check this in the documentation. If there is no improvement on this, can you reopen the issue so we can include it in our roadmap? Best Regards, |
Describe the bug
Hello,
I've encountered an issue with TreeSelect in PrimeNG 16 where the labels display an undesired '0' in front of each one. This problem is illustrated in the attached screenshot.
Additionally, the same bug can be observed on the official PrimeNG documentation site:
Could you please look into this matter and provide a fix for the unwanted '0' prefix in the TreeSelect labels? It impacts the user experience, and your prompt attention to this issue would be highly appreciated.
Thank you.
Environment
"primeng": "16.9.1"
"angular": "16"
Reproducer
https://stackblitz.com/edit/skfymg?file=src%2Fservice%2Fnodeservice.ts
Angular version
16
PrimeNG version
16.9.1
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
16.17.0
Browser(s)
No response
Steps to reproduce the behavior
No response
Expected behavior
No response
The text was updated successfully, but these errors were encountered: