Fix #2963: Allow access to ref

[melloware]

###Defect Fixes
Fix #2963: Allow access to ref

Many components were not forwarding the ref to the actual root elementRef of the component.

[mertsincan]

Hi @melloware,
I think we need to do a separate study for this. Maybe, all components can have two refs;

• <Carousel ref -> ref.current.customWidgetVariable/Function
• <Carousel elementRef -> elementRef.current (HTML dom element)

ref: component's ref
elementRef: DOM element's ref

WDYT?

[melloware]

So here is what I did I found every component where its ref was showing as grey and unused in VS Code.

Then I simply followed your example in other places where you already had an elementRef I just simply assigned it to the variable the user wants so its passed through as the ref like in the DropDown case.

But we can handle it any way you think is best I just followed how you were doing it other components!

[melloware]

Actually i think you might be right I am thinking that maybe we do this...

1. ref is always pointed at useImperativeHandle in all components even if it has no widget methods to expose YET like this...

    React.useImperativeHandle(ref, () => ({
        ...props
    }));

2. elementRef is always the root element of the component if its a DIV or SPAN or somethng.

[mertsincan]

Yes, I'm thinking :D

[melloware]

Closing this as its not the right PR.