Skip to content
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

Tree: styleClass of nodes is ignored #17579

Open
4 tasks
infe42 opened this issue Feb 5, 2025 · 0 comments · May be fixed by #17580
Open
4 tasks

Tree: styleClass of nodes is ignored #17579

infe42 opened this issue Feb 5, 2025 · 0 comments · May be fixed by #17580
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@infe42
Copy link

infe42 commented Feb 5, 2025

Describe the bug

The styleClass property of tree nodes is ignored and not added to the li element. This is a regression and worked in PrimeNG 17 and before.

Pull Request Link

#17580

Reason for not contributing a PR

  • Lack of time
  • Unsure how to implement the fix/feature
  • Difficulty understanding the codebase
  • Other

Other Reason

No response

Reproducer

https://stackblitz.com/edit/github-eps8r4ln-ogkppwd5

Environment

See Stackblitz.

The issue occurs with PrimeNG 18 and Angular 18.2 as well as with PrimeNG 19 and Angular 19.1. I have provided a Stackblitz for PrimeNG 19 and Angular 19.1.

Angular version

19.1.5

PrimeNG version

v19

Node version

No response

Browser(s)

No response

Steps to reproduce the behavior

  1. Go to Stackblitz.
  2. Check app.component.ts: Node "Node with styleClass" has a styleClass property
  3. Check running app: the styleClass is not attached to the li-Element of the tree node

Expected behavior

The li-Element of the tree node should have the style class that was defined in the styleClass property.

@infe42 infe42 added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Feb 5, 2025
@infe42 infe42 linked a pull request Feb 5, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant