You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem:
For example, if a file foo.thrift imports the file any.thrift and tries to references one of any.thrifts exports, the generated flow code will ultimately look like:
foo.js:
import any from './any';
type bar = {
a: any.baz,
}
at which point flow will report an error because it doesn't expect a . after the keyword any. I imagine this might happen with other file names that are flow-protected keywords.
The text was updated successfully, but these errors were encountered:
Problem:
For example, if a file
foo.thrift
imports the fileany.thrift
and tries to references one ofany.thrift
s exports, the generated flow code will ultimately look like:foo.js:
at which point flow will report an error because it doesn't expect a
.
after the keywordany
. I imagine this might happen with other file names that are flow-protected keywords.The text was updated successfully, but these errors were encountered: