Commit eebfa28
committed
Do not include types in JS blueprints
For the fallback case, where Ember's blueprints are being executed by a
version of Ember CLI earlier than 4.3.0, the emitted blueprints *must
not* include any TypeScript types, since the CLI will not be able to
remove the types. Accordingly:
1. Return a boolean flag from the `maybePolyfillTypeScriptBlueprints`
helper, indicating whether the blueprint is in a mode where it can
reliably *emit* types.
2. Use that new helper in the component blueprint so that it can avoid
emitting a signature type, and specifically can avoid emitting it
as a type parameter on the class or function default export.1 parent 8f9528e commit eebfa28
File tree
2 files changed
+24
-6
lines changed- blueprints
- component
2 files changed
+24
-6
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
8 | 8 | | |
9 | 9 | | |
10 | 10 | | |
11 | | - | |
| 11 | + | |
| 12 | + | |
12 | 13 | | |
13 | 14 | | |
14 | 15 | | |
15 | 16 | | |
16 | 17 | | |
| 18 | + | |
17 | 19 | | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
53 | 53 | | |
54 | 54 | | |
55 | 55 | | |
| 56 | + | |
| 57 | + | |
| 58 | + | |
| 59 | + | |
| 60 | + | |
| 61 | + | |
| 62 | + | |
| 63 | + | |
56 | 64 | | |
57 | 65 | | |
58 | | - | |
| 66 | + | |
59 | 67 | | |
60 | 68 | | |
61 | 69 | | |
| |||
264 | 272 | | |
265 | 273 | | |
266 | 274 | | |
267 | | - | |
268 | | - | |
| 275 | + | |
| 276 | + | |
| 277 | + | |
| 278 | + | |
| 279 | + | |
| 280 | + | |
269 | 281 | | |
270 | 282 | | |
271 | 283 | | |
272 | | - | |
273 | | - | |
| 284 | + | |
| 285 | + | |
| 286 | + | |
| 287 | + | |
| 288 | + | |
| 289 | + | |
274 | 290 | | |
275 | 291 | | |
276 | 292 | | |
| |||
0 commit comments