@umriss-ui/schedule 0.3.1 → 0.3.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +24 -0
- package/dist/schedule.js +989 -961
- package/docs/llms-full.md +6 -2
- package/package.json +3 -3
package/CHANGELOG.md
CHANGED
|
@@ -15,6 +15,30 @@ moves from here under the rule above.
|
|
|
15
15
|
|
|
16
16
|
---
|
|
17
17
|
|
|
18
|
+
## 0.3.3 – What you are working with (Sep. 2026)
|
|
19
|
+
|
|
20
|
+
### Changed
|
|
21
|
+
|
|
22
|
+
- **A selection steps the rest of the plan back.** The subtask that was
|
|
23
|
+
clicked keeps its task's full colour, the other subtasks of its task go
|
|
24
|
+
halfway to grey, and all other work - bars, dependencies, the strips of a
|
|
25
|
+
folded group - goes grey. The grey is the colour's own lightness without
|
|
26
|
+
its hue, so a label keeps its colour and greyed work never reads as
|
|
27
|
+
`"muted"`, which grows lighter instead. Findings keep their colours. A task
|
|
28
|
+
selected by its dependency, or through `selectedTask` alone, stays whole in
|
|
29
|
+
its colour; the ghost of a drag is always in full colour. Under forced
|
|
30
|
+
colours the selected task stays in the text colour and the rest takes
|
|
31
|
+
`GrayText`. Nothing to change for a caller: the picture follows the
|
|
32
|
+
selection the schedule already has.
|
|
33
|
+
|
|
34
|
+
---
|
|
35
|
+
|
|
36
|
+
## 0.3.2 – Core 0.13.0 (Sep. 2026)
|
|
37
|
+
|
|
38
|
+
Needs `@umriss-ui/core` 0.13; the peer range moves to `^0.13.0`. Nothing else changes for a caller.
|
|
39
|
+
|
|
40
|
+
---
|
|
41
|
+
|
|
18
42
|
## 0.3.1 – Core 0.12.0 (Sep. 2026)
|
|
19
43
|
|
|
20
44
|
Needs `@umriss-ui/core` 0.12; the peer range moves to `^0.12.0`. Nothing else changes for a caller.
|