Pass enableVirtualization flag to itwinui <Tree />

[anmolshres98]

Closes #1132

[grigasp]

@saskliutas, what do you think about this? IMO, our renderer should always use virtualization and the prop should not be available for consumers of our component.

[saskliutas]

@saskliutas, what do you think about this? IMO, our renderer should always use virtualization and the prop should not be available for consumers of our component.

I think it makes sense to allow consumer to decide whether virtualization is used or not. This TreeRenderer is one of the building blocks we provide so it might be used to build custom tree that do not require virtualization.

[grigasp]

@saskliutas, what do you think about this? IMO, our renderer should always use virtualization and the prop should not be available for consumers of our component.

I think it makes sense to allow consumer to decide whether virtualization is used or not. This TreeRenderer is one of the building blocks we provide so it might be used to build custom tree that do not require virtualization.

Sounds good. Should style prop also be changed to have effect?

[saskliutas]

@saskliutas, what do you think about this? IMO, our renderer should always use virtualization and the prop should not be available for consumers of our component.

I think it makes sense to allow consumer to decide whether virtualization is used or not. This TreeRenderer is one of the building blocks we provide so it might be used to build custom tree that do not require virtualization.

Sounds good. Should style prop also be changed to have effect?

I this this could be solved in a separate PR. We should probably also review if there are more props that are exposed but not propagated down to the base iTwinUI Tree component.

[grigasp]

@saskliutas, what do you think about this? IMO, our renderer should always use virtualization and the prop should not be available for consumers of our component.

I think it makes sense to allow consumer to decide whether virtualization is used or not. This TreeRenderer is one of the building blocks we provide so it might be used to build custom tree that do not require virtualization.

Sounds good. Should style prop also be changed to have effect?

I this this could be solved in a separate PR. We should probably also review if there are more props that are exposed but not propagated down to the base iTwinUI Tree component.

Filed a followup issue: #1137