@seatlayer/angular 0.115.0 → 0.116.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/README.md CHANGED
@@ -53,6 +53,24 @@ 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.0
57
+
58
+ Nothing needs a code change, and no type or prop changed. What a buyer may now see:
59
+
60
+ - **A held Season seat has a ✕.** Removing one seat from a Season hold lets the
61
+ whole hold go and holds the seats kept again as one new hold, so your
62
+ `onHoldChange` sees `null` and then a hold with a new operation id. The last
63
+ seat's ✕ simply releases it. There is no ✕ where your selection rules
64
+ (`numberOfPlacesToSelect`, `selectionValidators`) would refuse the seats
65
+ kept, nor while sales are closed.
66
+ - **Season single dates**, only on a Season the organizer sells by date as
67
+ well, with SeatLayer's own checkout, on a page that mints its own session:
68
+ step 1 offers "Single dates" beside the passes, and the buyer books the same
69
+ seat on the dates they tick, each at its own price, in one checkout.
70
+ Everywhere else nothing changes.
71
+ - **One version of the SDK.** If your app also installs `@seatlayer/js`
72
+ itself, move it to 0.116.0 as well.
73
+
56
74
  ## Upgrading to 0.115.0
57
75
 
58
76
  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,24 @@ 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.0
57
+
58
+ Nothing needs a code change, and no type or prop changed. What a buyer may now see:
59
+
60
+ - **A held Season seat has a ✕.** Removing one seat from a Season hold lets the
61
+ whole hold go and holds the seats kept again as one new hold, so your
62
+ `onHoldChange` sees `null` and then a hold with a new operation id. The last
63
+ seat's ✕ simply releases it. There is no ✕ where your selection rules
64
+ (`numberOfPlacesToSelect`, `selectionValidators`) would refuse the seats
65
+ kept, nor while sales are closed.
66
+ - **Season single dates**, only on a Season the organizer sells by date as
67
+ well, with SeatLayer's own checkout, on a page that mints its own session:
68
+ step 1 offers "Single dates" beside the passes, and the buyer books the same
69
+ seat on the dates they tick, each at its own price, in one checkout.
70
+ Everywhere else nothing changes.
71
+ - **One version of the SDK.** If your app also installs `@seatlayer/js`
72
+ itself, move it to 0.116.0 as well.
73
+
56
74
  ## Upgrading to 0.115.0
57
75
 
58
76
  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.115.0",
3
+ "version": "0.116.0",
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.115.0",
40
- "@seatlayer/js": "0.115.0",
39
+ "@seatlayer/core": "0.116.0",
40
+ "@seatlayer/js": "0.116.0",
41
41
  "tslib": "^2.8.1"
42
42
  },
43
43
  "peerDependencies": {