Add forwarding of refs for Header component

[andyrichardson]

Partially addresses #3819

[welcome]

💖 Thanks for opening this pull request! 💖

Here is a list of things that will help get it across the finish line:

• Run yarn lint locally to catch formatting errors. This will fix some errors automatically, commit and push any changes.
• Run yarn test locally to catch errors. This ensures all components still behave as they should.
• Run yarn start to run the doc site locally and try a few pages, ensuring everything is in good working order.
• Include tests when adding/changing behavior.

We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can.

[layershifter]

@andyrichardson hey!

This thing was missed, but it will be great to bump it. Are you still interested in it?

[andyrichardson]

@layershifter for sure! I just need to get it passing in CI?

[layershifter]

@andyrichardson great 👍 Yes, let me know if I can help somehow there.

P.S. please restore your fork as currently it's impossible to push changes 😺

[layershifter]

Actually, this change should happen in the definition i.e. const Header = React.forwardRef((props, ref) => {

• we have statics (Header.Content, Header.Subheader) and it will not be usable on default export
• a param for React.forwardRef() is a function, not component itself:

https://github.com/facebook/react/blob/41694201988c5e651f0c3bc69921d5c9717be88b/packages/react/src/ReactForwardRef.js#L38-L41

[layershifter]

You will probably will have many CI issues (at least with componentInfo), let's merge master and start fixing them 🧑‍🏭

[layershifter]

Closing for housekeeping 🏠 If you would like to follow up on it, feel free to create a new PR 🐱