fsanyoto commited on
Commit
d8c82a4
·
verified ·
1 Parent(s): 4a5c5df

Deploy AIOS web (React glide grid + FastAPI slice)

Browse files
RELEASES.json CHANGED
@@ -1,6 +1,12 @@
1
  {
2
- "current": "v27 (c05a794)",
3
  "releases": [
 
 
 
 
 
 
4
  {
5
  "version": "v27",
6
  "sha": "c05a794",
 
1
  {
2
+ "current": "v28 (2793e4b)",
3
  "releases": [
4
+ {
5
+ "version": "v28",
6
+ "sha": "2793e4b",
7
+ "date": "2026-08-18",
8
+ "subject": "release v28"
9
+ },
10
  {
11
  "version": "v27",
12
  "sha": "c05a794",
VERSION CHANGED
@@ -1 +1 @@
1
- v27 (c05a794)
 
1
+ v28 (2793e4b)
web/src/customer-grid/CustomerGrid.tsx CHANGED
@@ -3390,10 +3390,18 @@ function CustomerGridSurface({
3390
  ? current.map((item) => (item.id === view.id ? view : item))
3391
  : [...current, view];
3392
  });
 
 
 
 
 
 
 
 
3393
  const routed = routeQueryViewMutation(queryBinding, scope, {
3394
  id: eventId(queryBinding ? "query-view-update" : "view"),
3395
  type: "view_upsert",
3396
- view: view as unknown as Record<string, unknown>,
3397
  }, { query: mutateQueryWorkspace, native: emitHostEvent });
3398
  if (routed.channel === "refused")
3399
  signal(TOAST_EVENT, routed.refusal?.message ?? "That view change could not be saved.");
 
3390
  ? current.map((item) => (item.id === view.id ? view : item))
3391
  : [...current, view];
3392
  });
3393
+ // ⛔⛔ WAVE 35 QA — THE SAME RE-IDENTIFICATION THE AUTOSAVE NEEDS, AND THIS IS THE CALL SITE
3394
+ // THE TOOLBAR ACTUALLY USES. `persistView` is what Rows / Sort / Group / Hide fields go
3395
+ // through, so fixing only the autosave left every one of them still refused: measured on the
3396
+ // DEPLOYED build after the first fix — row height still raised *"…cannot take a second view"*
3397
+ // and `edited` stayed `false`. There are FOUR callers of the router in this file and the
3398
+ // identity belongs to the WRITE, not to one of them.
3399
+ // ⚠ Only the emitted subject moves; `setViews` above keeps the source view's own id.
3400
+ const subject = queryBinding ? { ...view, id: queryBinding.artifactId } : view;
3401
  const routed = routeQueryViewMutation(queryBinding, scope, {
3402
  id: eventId(queryBinding ? "query-view-update" : "view"),
3403
  type: "view_upsert",
3404
+ view: subject as unknown as Record<string, unknown>,
3405
  }, { query: mutateQueryWorkspace, native: emitHostEvent });
3406
  if (routed.channel === "refused")
3407
  signal(TOAST_EVENT, routed.refusal?.message ?? "That view change could not be saved.");
web/src/index.css CHANGED
@@ -3451,6 +3451,16 @@ body {
3451
  color: var(--lp-muted);
3452
  }
3453
 
 
 
 
 
 
 
 
 
 
 
3454
  .shell-side-bottom {
3455
  margin-top: auto;
3456
  padding: 8px 10px 10px;
 
3451
  color: var(--lp-muted);
3452
  }
3453
 
3454
+ /* ⛔⛔ WAVE 35 QA, SECOND PASS — TWO `auto` MARGINS SPLIT THE FREE SPACE BETWEEN THEM, and the
3455
+ first fix only took half. Giving `.shell-nav-templates` `margin-top: auto` while this band kept
3456
+ its own moved the row from 549 px above the account button to **280 px** — measured on the
3457
+ deployed build, which is the only reason it was caught. Flexbox distributes free space EQUALLY
3458
+ across every auto margin in the line; it does not hand it to the first one.
3459
+ ⭐ So the band yields when Templates is there to take it, and keeps its own pin otherwise. Three
3460
+ states, all deliberate: Templates VISIBLE -> band 0, the row lands against this border;
3461
+ Templates `.is-rail-hidden` (while `/nav` is in flight) -> the sibling rule does not match and
3462
+ the band's `auto` still pins the account row; Templates ABSENT from the DOM entirely -> same. */
3463
+ .shell-nav-templates:not(.is-rail-hidden) ~ .shell-side-bottom { margin-top: 0; }
3464
  .shell-side-bottom {
3465
  margin-top: auto;
3466
  padding: 8px 10px 10px;