Comment types of Flow makes Prettier confused

Prettier 1.15.1

Sorry, I could not reproduce it on v1.15.2 playground. 🙇 (solved at 1.15.2 ? 👀) Playground link

In flow, I can typecast with the following, not type-assertion.

Input:

type Props = {|
  ...$Exact<PropsWithTFn>,
  ...$Exact<$Call<typeof mapStateToProps, *, *>>,
  ...$Exact<$Call<typeof mapDispatch, *, *>>,
  ...$Exact<withResponse.WithQueryProps<RootQuery>>,
|};

However, this gets error message below in prettier 1.15.1

Replace `<$Call<typeof·mapDispatch,·*,·*>>` with `/*::·<$Call/*::·<typeof·mapDispatch,·*,·*>·*/>·*/`

Output:

type Props = {|
  ...$Exact<PropsWithTFn>,
  ...$Exact/*:: <$Call/*:: <typeof·mapStateToProps, *, *>*/> */
  ...$Exact/*:: <$Call/*:: <typeof mapDispatch, *, *>*/> */,
  ...$Exact/*:: <withResponse.WithQueryProps<RootQuery>*/> */,
|};

Expected behavior:

type Props = {|
  ...$Exact<PropsWithTFn>,
  ...$Exact<$Call<typeof mapStateToProps, *, *>>,
  ...$Exact<$Call<typeof mapDispatch, *, *>>,
  ...$Exact<withResponse.WithQueryProps<RootQuery>>,
|};

[ikatyang]

@j-f1 There’re two bugs in the example:

• /* :: (user.__typename: empty); */ -> (user.__typename: empty);
  • this is the long-standing one
• ...$Exact<PropsWithTFn>, -> ...$Exact/*:: <PropsWithTFn> */,
  • this one is somehow caused by /* :: (user.__typename: empty); */, it works fine if there’s no /* :: (user.__typename: empty); */

[j-f1]

would you allow me to attempt fixing the issue?

Please go ahead! We appreciate PRs.