@seatlayer/angular 0.115.0 → 0.116.1
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/README.md +35 -0
- package/dist/README.md +35 -0
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -53,6 +53,41 @@ npm install @seatlayer/angular
|
|
|
53
53
|
|
|
54
54
|
The component is **standalone**: import it directly, no NgModule needed.
|
|
55
55
|
|
|
56
|
+
## Upgrading to 0.116.1
|
|
57
|
+
|
|
58
|
+
Nothing needs a code change, and no type or prop changed. What a buyer may now see:
|
|
59
|
+
|
|
60
|
+
- **Season ✕ on a held seat:** Continue is disabled while the ✕ runs, instead
|
|
61
|
+
of ignoring the press.
|
|
62
|
+
- **Season single dates:** a price whose top is not known reads "from €25" in
|
|
63
|
+
the price list.
|
|
64
|
+
- **The map toolbar:** on a map about 500 px wide, Zones / Sections / Seats
|
|
65
|
+
takes its own row instead of sitting under Map / 3D.
|
|
66
|
+
- **Test mode:** the "Test mode" chip never covers seats. On a phone it sits in
|
|
67
|
+
the head of the sheet.
|
|
68
|
+
- **A Season with `theme.mode`:** its first step follows the mode, as its map
|
|
69
|
+
already did. Without a mode, nothing changes.
|
|
70
|
+
- **One version of the SDK.** If your app also installs `@seatlayer/js`
|
|
71
|
+
itself, move it to 0.116.1 as well.
|
|
72
|
+
|
|
73
|
+
## Upgrading to 0.116.0
|
|
74
|
+
|
|
75
|
+
Nothing needs a code change, and no type or prop changed. What a buyer may now see:
|
|
76
|
+
|
|
77
|
+
- **A held Season seat has a ✕.** Removing one seat from a Season hold lets the
|
|
78
|
+
whole hold go and holds the seats kept again as one new hold, so your
|
|
79
|
+
`onHoldChange` sees `null` and then a hold with a new operation id. The last
|
|
80
|
+
seat's ✕ simply releases it. There is no ✕ where your selection rules
|
|
81
|
+
(`numberOfPlacesToSelect`, `selectionValidators`) would refuse the seats
|
|
82
|
+
kept, nor while sales are closed.
|
|
83
|
+
- **Season single dates**, only on a Season the organizer sells by date as
|
|
84
|
+
well, with SeatLayer's own checkout, on a page that mints its own session:
|
|
85
|
+
step 1 offers "Single dates" beside the passes, and the buyer books the same
|
|
86
|
+
seat on the dates they tick, each at its own price, in one checkout.
|
|
87
|
+
Everywhere else nothing changes.
|
|
88
|
+
- **One version of the SDK.** If your app also installs `@seatlayer/js`
|
|
89
|
+
itself, move it to 0.116.0 as well.
|
|
90
|
+
|
|
56
91
|
## Upgrading to 0.115.0
|
|
57
92
|
|
|
58
93
|
Nothing needs a code change, and no type or prop changed. What a buyer may now see:
|
package/dist/README.md
CHANGED
|
@@ -53,6 +53,41 @@ npm install @seatlayer/angular
|
|
|
53
53
|
|
|
54
54
|
The component is **standalone**: import it directly, no NgModule needed.
|
|
55
55
|
|
|
56
|
+
## Upgrading to 0.116.1
|
|
57
|
+
|
|
58
|
+
Nothing needs a code change, and no type or prop changed. What a buyer may now see:
|
|
59
|
+
|
|
60
|
+
- **Season ✕ on a held seat:** Continue is disabled while the ✕ runs, instead
|
|
61
|
+
of ignoring the press.
|
|
62
|
+
- **Season single dates:** a price whose top is not known reads "from €25" in
|
|
63
|
+
the price list.
|
|
64
|
+
- **The map toolbar:** on a map about 500 px wide, Zones / Sections / Seats
|
|
65
|
+
takes its own row instead of sitting under Map / 3D.
|
|
66
|
+
- **Test mode:** the "Test mode" chip never covers seats. On a phone it sits in
|
|
67
|
+
the head of the sheet.
|
|
68
|
+
- **A Season with `theme.mode`:** its first step follows the mode, as its map
|
|
69
|
+
already did. Without a mode, nothing changes.
|
|
70
|
+
- **One version of the SDK.** If your app also installs `@seatlayer/js`
|
|
71
|
+
itself, move it to 0.116.1 as well.
|
|
72
|
+
|
|
73
|
+
## Upgrading to 0.116.0
|
|
74
|
+
|
|
75
|
+
Nothing needs a code change, and no type or prop changed. What a buyer may now see:
|
|
76
|
+
|
|
77
|
+
- **A held Season seat has a ✕.** Removing one seat from a Season hold lets the
|
|
78
|
+
whole hold go and holds the seats kept again as one new hold, so your
|
|
79
|
+
`onHoldChange` sees `null` and then a hold with a new operation id. The last
|
|
80
|
+
seat's ✕ simply releases it. There is no ✕ where your selection rules
|
|
81
|
+
(`numberOfPlacesToSelect`, `selectionValidators`) would refuse the seats
|
|
82
|
+
kept, nor while sales are closed.
|
|
83
|
+
- **Season single dates**, only on a Season the organizer sells by date as
|
|
84
|
+
well, with SeatLayer's own checkout, on a page that mints its own session:
|
|
85
|
+
step 1 offers "Single dates" beside the passes, and the buyer books the same
|
|
86
|
+
seat on the dates they tick, each at its own price, in one checkout.
|
|
87
|
+
Everywhere else nothing changes.
|
|
88
|
+
- **One version of the SDK.** If your app also installs `@seatlayer/js`
|
|
89
|
+
itself, move it to 0.116.0 as well.
|
|
90
|
+
|
|
56
91
|
## Upgrading to 0.115.0
|
|
57
92
|
|
|
58
93
|
Nothing needs a code change, and no type or prop changed. What a buyer may now see:
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@seatlayer/angular",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.116.1",
|
|
4
4
|
"description": "SeatLayer's official Angular seating chart and seat map SDK: live availability, seat selection, temporary holds, and a typed TypeScript API for ticketing apps.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"author": {
|
|
@@ -36,8 +36,8 @@
|
|
|
36
36
|
"typescript"
|
|
37
37
|
],
|
|
38
38
|
"dependencies": {
|
|
39
|
-
"@seatlayer/core": "0.
|
|
40
|
-
"@seatlayer/js": "0.
|
|
39
|
+
"@seatlayer/core": "0.116.1",
|
|
40
|
+
"@seatlayer/js": "0.116.1",
|
|
41
41
|
"tslib": "^2.8.1"
|
|
42
42
|
},
|
|
43
43
|
"peerDependencies": {
|