Fix #6083 TreeTable onSort

[KirilCycle]

Defect Fixes

Fix #6083

Apply sortField and sortOrder properties only during the first rendering

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Ignored Deployments

Name	Status	Preview	Comments	Updated (UTC)
primereact	⬜️ Ignored (Inspect)	Visit Preview		May 7, 2024 5:54pm
primereact-v9	⬜️ Ignored (Inspect)	Visit Preview		May 7, 2024 5:54pm

[melloware]

Hmm I am not sure this is correct. Did you look at DataTable? I feel like this was done on purpose if the user is using props.onSort they are controlling the sort so props.sort is applied else the internal sortState is used if PrimeReact is controlling the sort not the user.

[KirilCycle]

Hmm I am not sure this is correct. Did you look at DataTable? I feel like this was done on purpose if the user is using props.onSort they are controlling the sort so props.sort is applied else the internal sortState is used if PrimeReact is controlling the sort not the user.

Yes, I see what you mean, let me take a look at the DataTable

[KirilCycle]

Yes, you are right, DataTable behaves the same way as TreeTable, you need to manually control "sortField" and "sortOrder" to make it work. This approach is more flexible, but not as clear. I saw that primevue works similarly to this PR, even with onScroll it will work, but there is no way to control these parameters externally, does it make sense to control them externally?

[melloware]

Its the way its always been designed for right or wrong so I would leave it.