react-integration compiler options masks type issues

[seanforyou23]

Currently, our react-integration pkg serves the purpose of ensuring our documentation examples will build and compile as expected. It works great, but I recently realized strict type checking is turned off. Because of this, issues go undetected until they are happened upon by community members. Setting strict to true is standard practice and it doesn't make sense to suggest consumers lessen their compiler strictness just to be able to consume our components.

I've increased the strictness of the checks we can without making further changes in #3222.

This leaves us needing to work through changes required to enable the following compiler options:

• strictPropertyInitialization
• noImplicitAny
• strictNullChecks
• strictFunctionTypes

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[seanforyou23]

This is a critical issue, commenting so stale bot doesn't close it.

[dgutride]

@seanforyou23 - since the strict changes were made in #3222 is there some work this issue is still left open to capture?

[seanforyou23]

Hi @dgutride - yes we still have several strict modes left turned off. I was kinda thinking of this issue as an epic and linked out to them from this one so it's easier to follow this work as a sort of "theme" since it requires breaking changes. Does this help or answer your question? #3222 basically turned on the strict modes we could without causing any breaking changes to prevent new bits of code being added that would break one of these rules. Let me know if I should change anything about how they are captured.

[dgutride]

that makes sense - so we still need to enable them one by one and fix as we go - thx for the clarification!