[typescript] Improve type coverage of colDef

[flaviendelangle]

Fixes #2187

Other public methods that are not typed

• onStateChange is not typed (but may be removed [docs] Add missing API docs #2167)

[flaviendelangle]

@m4theushw I removed the event and props on some of the custom cell renderers because the typing says that they should not be here.
I would like your confirmation on this point 👍

[flaviendelangle]

Follow up on #2189 (comment)
If we want to stop exposing apiRef, I suppose that we don't want to type it on the public methods while it's still their.
The columns / colDef typing is still relevant I think.

[oliviertassinari]

How did we get away from the circular dependency in the types?

[flaviendelangle]

@oliviertassinari the type-only import ( import type { MyType } ) handles circular imports perfectly from what I read.
I'm not sure if, when importing a type with import { MyType } there is a real circular import issue or if it's just a limitation of the ESLint rule.

microsoft/TypeScript#35200
import-js/eslint-plugin-import#1453

[oliviertassinari]

@flaviendelangle Ok, I didn't know that TypeScript support circular type declaration. It sounds interesting to give it a try and see if it fly at scale or not. At least, we would have found and fixed other issues in the codebase.

[flaviendelangle]

I tried to build yarn release:build and the .d.ts files have been generated correctly.

https://github.com/mui-org/material-ui-x/pull/2213/files#diff-b98630eb301ddfb1b291caade7edafda784e434b852f21efc232324774d4857eR37
Here (other PR) I just fixed the circular import rather than adding type to dozens of imports.
But as long as our imports are only types (and if classes / enum, only used as types), this solution should work.

Alternatively, the import('...') syntax also support circular import. But it's heavier

api: import('../api/gridApi').GridApi