How does that solve the problem?

To be honest I don't really know. I noticed that the .sort method produced different results on Chrome and Firefox, indicating that the comparison function was not stable. Unstable sorting can be fixed by adding more logic to the comparison function and that's what I did.

Imagine a case there aChildType is array and bChildType is string. In those cases the old code returns 0, meaning that these elements "are the same", which is obviously not true, and we need to put the bChildType before aChildType (string before array). This new code does that.

I tested with many different inputs and they all worked, so this shouldn't break anything.

Looks like this has been fixed, I assume in this change, so I'll close this PR.

Looks like this has been fixed, I assume in this change, so I'll close this PR.

No, this commit improves type support only. We can keep this open.

@AykutSarac That other change has some logic changes too:

and

Nevermind my other comment, it's still a bit broken so this PR is still needed. I'll check those merge conflicts tomorrow.

@AykutSarac any updates? I've fixed the merge conflicts.