strothj

Another thing to note is that `useMemo` is a performance optimization with no hard guarantee that it won't be recalculated. React can choose to recalculate memoized values (https://reactjs.org/docs/hooks-reference.html#usememo).

Thank you for the issue report! I will investigate this tomorrow (Sunday).

Hello, I've been trying to reproduce this issue but haven't had success. Can you upload a minimal example repo? Also are you sure you have the latest version installed, there...

I've added a branch with your example: https://github.com/strothj/react-docgen-typescript-loader/tree/bug/component-with-enum/packages/react-docgen-typescript-loader-example/src/components/ComponentUsingEnum Can you check that I was understanding correctly?

@justinanastos I'm closing this issue for house keeping purposes. Feel free to open a new issue. @realalexhomer Your issue appears to have been fixed upstream. It works fine now from...

The TypeScript library itself has the concept of a `project` and it's associated loaded files. There was actually a recent pull request which was merged that sped up the parsing...

> @stevehanson (or anyone else), what is the reason you need to add > > ``` > options: { > presets: [require.resolve('babel-preset-react-app')], > }, > ``` > to make this...

> Thank you @stevehanson for your solution! @teddybradford I created a full sample repo that others can use, could be linked to in the documentation I guess :) > https://github.com/johot/storybook4-cra2-typescript-react-docgen-typescript-demo...

I think that instead of using `@storybook/addon-info`, you'd use: https://github.com/tuchk4/storybook-readme

You're right. Can't believe I missed that. My initial impression is that something changed from the very old v4 alpha and the current stable build of Storybook. My guess is...