@autobusal/common 1.29.0 → 1.31.0
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 +18 -0
- package/Viewer/styles.ts +23 -5
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,6 +1,24 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
3
|
|
|
4
|
+
## 1.31.0
|
|
5
|
+
|
|
6
|
+
### Added
|
|
7
|
+
|
|
8
|
+
- **A `row-component` field spans the full row width**, same as `row-textarea-html` already did - what lets a Viewer form's own section headings (`SectionHeading`, admin-label's Content/styles.ts) sit as a full-width divider instead of sharing a row with whatever field lands beside them.
|
|
9
|
+
|
|
10
|
+
## 1.30.0
|
|
11
|
+
|
|
12
|
+
### Changed
|
|
13
|
+
|
|
14
|
+
- **`Viewer`'s field grid stays at two columns on every screen width.** It
|
|
15
|
+
used to widen to three columns at >=1300px - fine for a form of
|
|
16
|
+
independent, unrelated fields, but a form built for a two-column rhythm
|
|
17
|
+
(one field, a divider row, a related pair, a divider row, ...) reflows
|
|
18
|
+
into three and starts mixing fields from different logical groups onto
|
|
19
|
+
the same row, with nothing to say which group a given row belongs to.
|
|
20
|
+
Affects every Viewer-based form in the app, not just admin-label's.
|
|
21
|
+
|
|
4
22
|
## 1.29.0
|
|
5
23
|
|
|
6
24
|
### Added
|
package/Viewer/styles.ts
CHANGED
|
@@ -28,7 +28,7 @@ export const Container = styled.div`
|
|
|
28
28
|
|
|
29
29
|
/*
|
|
30
30
|
* Edited: Ferjolt Ozuni - Date: 2026-08-07
|
|
31
|
-
* A rich-text editor gets the full row
|
|
31
|
+
* A rich-text editor gets the full row - even at half the width it has
|
|
32
32
|
* less room for its own toolbar than for the text, and every consumer
|
|
33
33
|
* that uses one wants it wide - so this belongs here rather than as a
|
|
34
34
|
* flag each caller has to remember to pass.
|
|
@@ -36,13 +36,31 @@ export const Container = styled.div`
|
|
|
36
36
|
& > div.row-textarea-html {
|
|
37
37
|
flex-basis: 100% !important;
|
|
38
38
|
}
|
|
39
|
-
}
|
|
40
39
|
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
40
|
+
/*
|
|
41
|
+
* Edited: Ferjolt Ozuni - Date: 2026-08-08
|
|
42
|
+
* A 'component' row gets the full width too, same reasoning as
|
|
43
|
+
* row-textarea-html above - it is how a form's own section headings
|
|
44
|
+
* (SectionHeading, see admin-label's Content/styles.ts) span the row
|
|
45
|
+
* instead of sharing it with whatever field happens to land beside
|
|
46
|
+
* them.
|
|
47
|
+
*/
|
|
48
|
+
& > div.row-component {
|
|
49
|
+
flex-basis: 100% !important;
|
|
44
50
|
}
|
|
45
51
|
}
|
|
52
|
+
|
|
53
|
+
/*
|
|
54
|
+
* Edited: Ferjolt Ozuni - Date: 2026-08-08
|
|
55
|
+
* DELIBERATELY no wider breakpoint pushing this to three columns - it
|
|
56
|
+
* used to (>=1300px, flex-basis 33%), and the result was a grid with no
|
|
57
|
+
* visual boundary between one logical group's fields and the next: a
|
|
58
|
+
* form built for a two-column rhythm (field, spacer-row, field pair,
|
|
59
|
+
* spacer-row, ...) reflowed into three columns and mixed unrelated
|
|
60
|
+
* fields onto the same row. Every admin-label tab (and every other
|
|
61
|
+
* Viewer-based form in the app) now stays at the same two-column layout
|
|
62
|
+
* from 540px up, at any screen width.
|
|
63
|
+
*/
|
|
46
64
|
`;
|
|
47
65
|
|
|
48
66
|
export const ContainerActions = styled.div`
|