We started using the same logic for union and intersection but then added a special case for `a & {}`. It turns out that they should be handled completely differently in practice.
The heuristic i'm using is if you go from object to non-object or vis-versa, then inline, otherwise go to the next line and indent (like &&).
Fixes #864
Fixes #1017
10 lines
271 B
JavaScript
10 lines
271 B
JavaScript
export type ReallyBigSocketServer = ReallyBigSocketServerInterface & ReallyBigSocketServerStatics;
|
|
|
|
type Props = {
|
|
focusedChildren?: React.Children,
|
|
onClick: () => void,
|
|
overlayChildren?: React.Children,
|
|
style?: Object,
|
|
thumbnail: ImageSource,
|
|
} & FooterProps;
|