Noviny

In general, we’ve put magic into pretty-proptypes (you can override all type definitions using its API). Since it’s an AST type, we should support it. What part is actually the...

Oh, Pick and Exclude.

Hey Sam! Thanks for raising this issue! It's a good idea, with some design constraints/history worth knowing about before diving in to it. We actually used to do this (on...

ps. If you want to just use multiple exports now, you can via this exported function that we have failed to document: https://github.com/atlassian/extract-react-types/blob/a972d1080fd03810b8338837df5c4e3e16cdbd9f/packages/extract-react-types/src/index.js#L1603-L1614

Build be failing - second thing on this: Can you make an issue (for me) to publish a final version of the old packages with a readme comment redirecting people...

Issue makes sense - just commenting that if you are only using typescript, we've also built a library called [magical types](https://github.com/Thinkmill/magical-types) that's basically this but slightly better because it only...

This sounds absolutely correct, this shouldn't be a global.

We are using a custom pathResolution function! I have finally accepted the obvious truth that this was a bad idea, so will be looking to replace it in the future....

Hm. Digging into this a bit, we are likely to need two ways to resolve paths in `codesandboxer-fs`. One which we use for comparing and writing js paths, and one...

@adeelibr Hey! Help on this would be greatly appreciated! There's sort of two parts here. First is just getting good tests around this. I think some of the integration tests...