0f54d6c4a5
In environments such as the Language Service where inline type-checking code is not supported, the compiler would previously produce a diagnostic when a template would require inlining to check. This happened whenever its component class had generic parameters with bounds that could not be safely reproduced in an external TCB. However, this created a bad user experience for the Language Service, as its features would then not function with such templates. Instead, this commit changes the compiler to use the same strategy for inline TCBs as it does for inline type constructors - falling back to `any` for generic types when inlining isn't available. This allows the LS to support such templates with slightly weaker type-checking semantics, which a test verifies. There is still a case where components that aren't exported require an inline TCB, and the compiler will still generate a diagnostic if so. Fixes #41395 PR Close #41513 |
||
|---|---|---|
| .. | ||
| bundles | ||
| ivy | ||
| src | ||
| test | ||
| BUILD.bazel | ||
| api.ts | ||
| build.sh | ||
| index.ts | ||
| package.json | ||