[AppBar] Fix type support of overridable component

[heleg]

• I have followed (at least) the PR section of the contributing guide.

Added the OverridableComponent to AppBar.

Can somebody help me to understand why proptypes generator insistently removes component prop and @default annotation from js file? It's not easy to understand how typescript-to-proptypes and generateProptypes.ts works, so I gave up.

[mui-pr-bot]

No bundle size changes

Generated by 🚫 dangerJS against 0555248

[oliviertassinari]

Can somebody help me to understand why proptypes generator insistently removes component prop and @default annotation from js file? It's not easy to understand how typescript-to-proptypes and generateProptypes.ts works, so I gave up.

Removing the component sounds correct. On the other hand, removing the default color value, seems to be unexpected. cc @eps1lon.

[heleg]

I just started to figure out how it works. Please help me to understand why yarn docs:api removed all the AppBar api docs. That's why CI didn't pass. It doesn't look like I changed anything that could make such thing.

[oliviertassinari]

I had a look. It seems that the generation scripts were failing because the types are wrong. I have pushed a commit to follow the other components in the codebase. Not sure if it's enough but it seems to work. I'm moving to a different effort. A thorough review would be great.

[oliviertassinari]

I have rebased to leverage the latest fix Sebastian did.

[oliviertassinari]

I'm moving forward with it as the issue we asked the help of Sebastian for is no longer reproducing. We manage to get away without by using the standard way the component types in the rest of the codebase. We also have new test cases in case we need to further iterate.

[heleg]

@oliviertassinari Sorry for not participating anymore.. Too many new things for me.