Daniel

Before merging, I'll have to go back through again and add changes to the GitHub readme, such as Localization.

I've added Localization but I couldn't get the table to format. Are markdown tables supported or do we need to reformat?

Thanks! My mac must have removed them in the copy/paste bc I don't think I deliberately removed them. Anyway, here's how the table looks now. Any ideas as to how...

Yes plz 👍

Maybe a subcategory on the docs page for experimental / untested “at your own risk” features? And then after a period of time transition those features into the core set...

I would like to know whether my approach for this PR is the right direction before I continue to work on generics. The goal is to get the auto-generated [types/index.ts](https://github.com/parse-community/Parse-SDK-JS/blob/6816d7b1a36f0ceffded3296dc99f099e9bcb253/types/index.d.ts)...

I would also expect that if we move to this and shift the example repo to ts, there will be a number of expected issues arise. The main one i've...

I think the thing that is missing from [this](https://github.com/parse-community/parse-server/pull/7337#issuecomment-817395936) seems to be the fact that the types for Parse.Object, Parse.Cloud, need to come from the repo that `require('parse')` comes from....

> The reason is that it seems to be challenging to reliably generate quality TS from JSDoc Just FYI the [type defintions](https://github.com/parse-community/Parse-SDK-JS/blob/6816d7b1a36f0ceffded3296dc99f099e9bcb253/types/index.d.ts) in this PR are automatically generated from the...

The main thing holding this PR back is support for generics and passing ts tests. If anyone has any skills in these areas let me know 😊