-
Notifications
You must be signed in to change notification settings - Fork 486
4.0.0.rc.0 broken #749
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
Comments
Ok more info, it's flow specific... I'm importing types as
(I'd use named exports but babel, or perhaps tcomb, is enforcing the use of .default) I then access the types such as the following, which is what breaks documentation.js
|
Previously we naively thought that id.name would be a string for all types, which is not the case. Instead, we use babel-generator to safely generate string representations of types. Fixes #749
Previously we naively thought that id.name would be a string for all types, which is not the case. Instead, we use babel-generator to safely generate string representations of types. Fixes #749
Thanks for the bug report! I've isolated this issue to a flow type with a property in it. I can also replicate this issue in beta.19 so maybe you upgraded from something older than that? I have a fix and an expanded test suite in the PR: #751 |
Previously we naively thought that id.name would be a string for all types, which is not the case. Instead, we use babel-generator to safely generate string representations of types. Fixes #749
Having upgraded I now get...
The text was updated successfully, but these errors were encountered: