Material-ui: [Transition] Expose internal component?

[cherniavskii]

In this example Collapse component is used with unmountOnExit property, which is passed to its inherited component Transition.
Transition is not present in Component API docs, since it is internal.

So maybe it's worth to expose that component?
It will also add a possibility to write own transitions easier.

[oliviertassinari]

This is a good question! The current situation is tricky:

• We have been forking react-overlays in order to fix bugs inside it. Hence this internal Transition component.
• They merged react-overlays back to react-transition-group.
• We have been upgrading react-transition-group in order to use the latest changes on the Ripple component.
• Turns out, they have fixed some core issue with react-transition-group that we haven't as I have discovered with #7888.

So, we have some options:

• #7888
  
  
  
  1. We cherry-pick react-transition-group fixes
  
  
  2. We remove our Transition component to rely on react-transition-group
  
  
• Bundle size
  
  
  
  1. Remove react-transition-group dependency and duplicate their code to minimize code duplication
  
  
  2. We remove our Transition component to rely on react-transition-group
  
  
• Developer Experience
  
  
  
  1. We make our Transition component public
  
  
  2. We advise people to use react-transition-group
  
  

[rosskevin]

If at all possible, let's use the external project. I don't see a need to maintain that here; am I missing something in that regard?

[oliviertassinari]

There is no more internal Transition component. No need to expose it 🙃. Instead, the documentation points to react-transition-group.