Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Addon-docs: Improve basic support for Flow props #8890

Merged
merged 2 commits into from
Nov 20, 2019

Conversation

patricklafrance
Copy link
Member

Issue:

What I did

Improved the basic support for Flow.

Before the improvement for PropTypes the support for Flow was better than it is now. This PR fix that.

This is also a first step to generalize some concepts of PropTypes to other type systems.

How to test

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

To test with Jest run: yarn jest --testPathPattern=createPropDef

If your answer is yes to any of these, please make sure to include it in your PR.

@vercel
Copy link

vercel bot commented Nov 19, 2019

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/ifuf924ot
🌍 Preview: https://monorepo-git-props-table-flow-type-basic-support.storybook.now.sh

@shilman shilman changed the title Improve basic support for Flow Addon-docs: Improve basic support for Flow props Nov 20, 2019
Copy link
Member

@shilman shilman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

GREAT! 😻

@shilman shilman merged commit d6a0247 into next Nov 20, 2019
@shilman shilman deleted the props-table-flow-type-basic-support branch November 20, 2019 01:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants