[ExpansionPanelSummary] Fix event forwarding

[jmetev1]

Closes #13577 and adds test for it.

I wasn't clear on what I should change proptypes to. onchange and onclick are in proptypes now, but they're ignored from the generated docs. Is that done for some reason? Should onfocus and onblur be added there but with @ignore for some reason? I can update it to whatever is desired style.

[oliviertassinari]

@jmetev1 It's a great first pull request on Material-UI 👌🏻. Thank you for working on it!

[oliviertassinari]

Is that done for some reason?

We avoid documenting the native properties, it would be noise to our users.

[oliviertassinari]

Should onfocus and onblur be added there but with @ignore for some reason? I can update it to whatever is desired style.

Good question, we used to have an eslint rule that ask for defining all the proptypes of the properties we use. It seems that eslitn rule is no longer working 😱. It's this rule to be specific: https://github.com/yannickcr/eslint-plugin-react/blob/master/docs/rules/prop-types.md. Do you want to look into this problem?

[jmetev1]

thank you. I'm looking at eslint rule problem now. looks like some kind of conflict with another rule. trying to narrow it down now. @oliviertassinari

[oliviertassinari]

@jmetev1 Let us know if you can find anything! I doubt we are the only one affected.

[jmetev1]

Well i now know far more than i used to about eslint config. So this has been talked about already jsx-eslint/eslint-plugin-react#1958 So package.json had "eslint-plugin-react ^7.4.0". And yarn.lock had 7.11.1, which is the latest. So that's what I was working with. In that link the eslnt-plugin-react people say it's fixed but they haven't published. The problem appears to be use of spread operators. And i confirmed that when I made a simple component with no spread operators, failure to document prop types did get correctly flagged when using 7.11.1. So since they said it was published, I grabbed the newest copy of repo from their repo and dropped it in to node modules. And now it correctly flags props that are used but not documented even with spread operator. As mentioned in that link, another work around is dropping back to 7.10.0. But that causes some problems with eslint airbnb package. And eslint-pulgin-react people haven't published since august. Someone even asked jsx-eslint/eslint-plugin-react#2046 and the answer wasn't super encouraging. Soooo. I don't see much of any solution unless someone wants to fork the eslint-plugin-react repo and point package.json to that directly or something messy like that. Thanks for reading my novel! @oliviertassinari

[oliviertassinari]

@jmetev1 I believe our setup is pretty common, let's wait. I hope they will sort the issue out. Thank you for the investigation!