Manuel

> ## ⚠️ Important change for merging PRs from Parse Server 5.0 onwards! > > We are planning to release the first beta version of Parse Server 5.0 in October...

@mstniy Please feel free to request a review once this is ready.

@mstniy Do you think you could resolve the conflicts so we can prepare this PR for merge?

> ## ⚠️ Important change for merging PRs from Parse Server 5.0 onwards! > > We are planning to release the first beta version of Parse Server 5.0 in October...

Are you saying that using flow-to-ts mixes [point 2 with 3](https://github.com/parse-community/parse-server/issues/7334#issuecomment-817114222) or even require 3 before 2? That is what I [meant](https://github.com/parse-community/parse-server/issues/7334#issuecomment-817224528) and what makes this approach so difficult. If...

> The most suitable way forward, would probably be to complete type definitions in current flow codebase and once we can reduce this number of errors to almost zero, use...

The flow-to-ts module has no option to simply ignore non-annotated code?

> When you run TSC after that, it generate errors because of missing annotations, or use of any types. Oh, the errors do not come from `flow-to-ts` but from TS?...

> If the goal for now is only to generate Typescript definitions, and NOT replace the codebase with Typescript entierly (aka case (2)) : That is what I believe. Replacing...

> Correct me if in wrong, but from what I've seen, #7335 does generate JSDoc and .d.ts declarations, but thoses declarations even if they exists and contains parameters, everything is...