[docs] Use immediate export when there is no HOC part 2

[merceyz]

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

Followup to #16005, VSCode failed to find and replace all the instances on the first try. Used formattedTSDemos to do it correctly this time

[mui-pr-bot]

No bundle size changes comparing 396e379...36c4dd6

Generated by 🚫 dangerJS against 36c4dd6

[eps1lon]

I appreciate the effort but this is a lint rule in disguise and we should have a discussion about those. It is IMO wasteful to introduce lint rules into the codebase without any rationale. They add diff noise and require a conscious code style shift when working on this codebase.

Is there a rational for

-function foo() {}
-export default foo;
+ export default function foo() {}

?

[merceyz]

See #16003 (comment)

[eps1lon]

So "shorten the demos". Not a fan but makes sense. Still better implemented with a lint rule. I can take care of that in another PR.

[oliviertassinari]

I would emphasize the value on "not having to duplicate the component name". It's one less degree of freedom (so you can't use two different names by mistake). This is only marginally better, it won't change thing much at the end of the day. I believe it's one of those small details that compounds.

[oliviertassinari]

@merceyz Can we split the effort? I propose that we remove the automatic generation part of this pull request that has controverse around it. This way, we can benefit from the documentation improvement by merging it. It will also make the review of the eslint or code generation logic easier in the next pull request.

[merceyz]

@oliviertassinari Sure, I ran the command again to update the remaining demos and reverted the changes to formattedTSDemos.

[oliviertassinari]

Perfect!