[MenuItem][Table][Tabs] Hide internal properties in docs

[heetvachhani]

• PR has tests / docs demo, and is linted.
• Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
• Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

A number of props that are controlled by a parent component are visible in the docs. This PR hides them.

Some of the table click / hover in particular cause confusion, as they appear to offer functionality that doesn't exist. While this should be fixed at some point (parent component should attach to a separate internal use callback prop), for now hiding them will reduce confusion.

The associated issue lists all the components that have been checked.
Closes #3588.

[mbrookes]

@heetvachhani - please don't squash until we're ready to merge, it makes it hard to see what's changed.

[heetvachhani]

okay sure will take care of it next time 😁

[mbrookes]

Why?

[mbrookes]

I hope so! Please squash.

[mbrookes]

@callemall/material-ui - please take a look and merge if you're happy.

[alitaheri]

Some tags are before the description and some are after. Please be consistent. Guys do you think it should be after or before? I'm not sure myself O.o

[mbrookes]

Good catch, I spotted this and meant to come back to it after we were done chasing and tracing to figure out which ones to @ignore.

I just had a look at what's been done previously, and most of the existing ones are before, but some are after, so there is no consistency. Also Stepper has just introduced a ton of internal props, and they're all after.

It would be good to be consistent, but I don't mind which. Before is perhaps a little more explicit.

[alitaheri]

Yeah might not be a bad idea to keep after only for function signature. so signature and @ignore won't get mixed up 👍

[alitaheri]

Better have a PR making all consistent afterward 👍

[alitaheri]

@newoga @oliviertassinari Any objections? If none merge, thanks 👍 👍

[mbrookes]

might not be a bad idea to keep after only for function signature. so signature and @ignore won't get mixed up

Can we get a custom eslint rule for that? 😄

[heetvachhani]

@mbrookes I have made all the @ignore tag consistent so merge it if there isn't any problem. Thanks 👍

[newoga]

@heetvachhani Can you squash this? Thanks!

[heetvachhani]

Done @newoga !

[oliviertassinari]

@heetvachhani Good work 👍.

[alitaheri]

Thanks @heetvachhani 👍 👍

[ngbrown]

@heetvachhani I think you overdid the @ignore on the Table components.

For TableHeaderColumn, there's no way to know if a column header was clicked except for the onClick which was hidden from the documentation.

The same applies to all TableRowColumn that are in a TableFooter. If the developer wants to detect a click or hover on a footer cell, then they would need use event handlers directly on the TableRowColumn and they should be in the documentation..

Why is adjustForCheckbox hidden in the documentation for TableFooter if it's not hidden for TableHeader? Nothing internally sets it.