bindCallback: resultSelector destructuring callback argument if it's array

[ArtemNikolaev]

Describe the bug

bindCallback(fnCb, resultSelector);

if callback in fnCb looks like cb(arg1); - resultSelector will work as function (arg1) {...}
if callback in fnCb looks like cb(arg1, arg2, ..., argN) - resultSelector will work as function (arg1, arg2, ..., argN) {...}
This is expected behavior, the problem is:

if callback in fnCb looks like cb( [ val1, val2, ..., valN ])(single argument, which is array) - resultSelector will work as function (val1, val2, ..., valN) {...}

Expected behavior

for callback call which looks like cb( [ val1, val2, ..., valN ])(single argument, which is array) - resultSelector should work like
funciton (arg1) {...}, where arg1 is [ val1, val2, ..., valN ]

Reproduction code

function fnCallback4(val, cb) {
    cb(['otherFromCallback', val, 'otherFromCallback']);
}
function resultSelector4(arg1, arg2, arg3) {
    return ['otherFromResultSelector', arg1, arg2, arg3, 'otherFromResultSelector'];
}

const bC4 = bindCallback(fnCallback3, resultSelector3);
bC4('bla').subscribe(console.log);

Reproduction URL

No response

Version

7.8.1

Environment

nodejs 21.4.0

Additional context

No response

[ArtemNikolaev]

Also see same behaviour on bindNodeCallback

[benlesh]

Hi @ArtemNikolaev — thank you for taking the time to open this issue and for sharing your thoughtful feedback with the RxJS project. I’m sorry it took us so long to respond. Given how much time has passed and the lack of recent activity, I’m going to close this for now so the tracker reflects the work we’re likely to act on. If this is still relevant on a current RxJS release, please feel welcome to open a new issue with updated context and a reproduction. Thank you again for your contribution and patience.

— Ben