Fix #3107: ImperativeHandle put props first

[melloware]

###Defect Fixes
Fix #3107: ImperativeHandle put props first

So the properties don't clobber methods like filter

[mertsincan]

Maybe, it can be like;

this.dtRef.current.props.first  instead of this.dtRef.current.first

Exp;
const datatableInstance = this.dfRef.current;

datatableInstance.props.first
datatableInstance.resetFilter
...

WDYT?

[melloware]

@mertsincan that is what I wanted to do but it wouldn't let me do this...

    React.useImperativeHandle(ref, () => ({
        props: ...props,
        getElement: () => elementRef.current
    }));

The only thing i could see doing was ...

    React.useImperativeHandle(ref, () => ({
        getProps: () =>  ...props,
        getElement: () => elementRef.current
    }));

But not sure I liked that either. Any help here would be appreciated!

[mertsincan]

Could you please try;

React.useImperativeHandle(ref, () => ({
        props,
        getElement: () => elementRef.current
}));

What error do you get when you use it?

[melloware]

Let me try...

[melloware]

DUH! that works great and is exactly what we want. I just updated the PR.