P-Splitter: Does not respect minSizes array after upgrading to 17.16.1

[JCarusWTW]

Describe the bug

We have a p-splitter in our code, with a minSizes array of [25,25] being passed in. We have recently upgraded the primeng version from 16.9.1 to 17.16.1 and the minSizes array is no longer being respected i.e. whereas you used to be unable to drag the p-splitter handle past the minimum of 25% size for either panel, the user is now allowed full resizing between 0 and 100% of the possible size despite the 25% minimums still being in the code. You can reproduce the issue purely by switching between versions (no code changes).

Environment

Windows, typescript, version 17.16.1 for primeng

Reproducer

https://github-7cfjki.stackblitz.io

Angular version

17.3.8

PrimeNG version

17.16.1

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

20.11.0 and/or 21.6.1

Browser(s)

No response

Steps to reproduce the behavior

1. Use splitter on stackblitz and note the fact that you can drag the handle anywhere within the two panels
2. Go to package.json, change line 9 (version of primeng) to 16.9.1, ensure it rebuilds
3. Use the splitter and note that you cannot resize either panel smaller than 25% (as set in minSizes array in html file)

Expected behavior

I expect the behaviour from v17 to match that of v16 (and the docs) i.e. if minSizes is set to 25,25 then the user should be unable to resize either panel to smaller than 25%.

[PranKe01]

I can confirm this bug. It also does not work in primeng components demo page.

[raiworld81]

+1

[heiooyooy]

+1
The pull request #14646, commit no: b3e91c7 created this issue.
"add input transform numberAttribute" to minSizes of splitter, which is a number[], not a number, was apparently a mistake.
please fix this issue thanks.

[PranKe01]

@cetincakiroglu Probably a duplicate of issue #15629. Looks like a low hanging fruit, which should be easy to fix. Would be nice if it would get fixed with next version (: