Addon-docs: Fix React.forwardedRef/memo props

[darmawanalbert]

Issue: #7933

What I did

Fix Props block rendering issue when using React.forwardRef by checking whether the target should be calling render() first to get the list of propTypes or not.

How to test

• Is this testable with Jest or Chromatic screenshots? No
• Does this need a new example in the kitchen sink apps? No
• Does this need an update to the documentation? No

[vercel]

This pull request is being automatically deployed with ZEIT Now (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://zeit.co/storybook/monorepo/pude9nc6y
🌍 Preview: https://monorepo-git-fork-darmawanalbert-addon-docs-forward-ref-props.storybook.now.sh

[shilman]

Thank you @darmawanalbert -- this is really awesome!!

This code makes sense, but since it's React-specific, would it be possible to put it inside the getPropDefs function returned from inferPropDefs?

Also, if it's a similar fix, would you mind also adding React.memo support and test case while you're at it?

[shilman]

Meant to request changes in my prev review :)

[darmawanalbert]

@shilman sure, let me try it on React.memo()

[darmawanalbert]

@shilman I have added another logic to fix React.memo case and move it to getPropDefs function 🙇

[shilman]

This is freakin' awesome @darmawanalbert! Thanks so much for the fix!!!