Commit a63033f
committed
[RFC] Remove build phases
As discussed today between @matz3, @tommyvinhlam, @codeworrior, @RandomByte
Build phases would allow for more precise extensibility of a types build
execution. Mainly scenarios where only a single task should be replaced
or added could overwrite one of the build phases to hook in-between of
certain sets of tasks.
Instead, they will have to overwrite the whole build function containing
all tasks. The main reason for this decision is the lack of known
extensibility use-cases. Therefore we do not want to decide on the
naming and semantics of any build phases yet as changing them later on
will hardly be possible.1 parent 4e1252f commit a63033f
1 file changed
+6
-30
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
22 | 22 | | |
23 | 23 | | |
24 | 24 | | |
25 | | - | |
26 | | - | |
27 | | - | |
28 | | - | |
29 | | - | |
30 | | - | |
31 | | - | |
32 | | - | |
33 | | - | |
34 | | - | |
35 | | - | |
36 | | - | |
37 | | - | |
38 | | - | |
39 | | - | |
40 | | - | |
41 | | - | |
42 | | - | |
43 | | - | |
44 | | - | |
45 | | - | |
46 | | - | |
47 | | - | |
48 | | - | |
49 | | - | |
50 | | - | |
51 | | - | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
52 | 28 | | |
53 | 29 | | |
54 | 30 | | |
55 | 31 | | |
56 | | - | |
57 | | - | |
58 | | - | |
| 32 | + | |
| 33 | + | |
| 34 | + | |
59 | 35 | | |
60 | 36 | | |
61 | 37 | | |
| |||
0 commit comments