@bakers-build/addon-bakers-ui 0.1.2-next.194 → 0.1.2-next.206

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.
Files changed (3) hide show
  1. package/dist/src/Entity/ticket/Form/edit.d.ts +5 -6
  2. package/dist/src/Entity/ticket/Form/edit.js +5 -6
  3. package/package.json +3 -3
package/dist/src/Entity/ticket/Form/edit.d.ts CHANGED
@@ -11,11 +11,10 @@ export type EditFieldId = 'assignee' | 'reviewers' | 'conductor' | 'estimate' |
11
11
  * `cancelled`, so no served fact carries the cancel edge. The precedent is
12
12
  * `STATE_FILTER_VALUES` in `Data/query.ts`, hardcoded for the same reason.
13
13
  *
14
- * One constant serves every ticket workflow because in ALL of them
15
- * (`bb_work`, `bb_deployment`, `bb_verification`) `cancel.from` is exactly
16
- * the set of non-terminal states — so "non-terminal" and "the workflow permits
17
- * cancelling" are the same predicate, and no workflow id is needed to tell
18
- * them apart.
14
+ * One constant serves every ticket workflow because in the ticket workflow
15
+ * (`bb_work`) `cancel.from` is exactly the set of non-terminal states — so
16
+ * "non-terminal" and "the workflow permits cancelling" are the same
17
+ * predicate, and no workflow id is needed to tell them apart.
19
18
  */
20
19
  export declare const CANCELLED_STATE = "cancelled";
21
20
  /**
@@ -29,7 +28,7 @@ export declare const CANCEL_TICKET_ACTION_ID = "cancelTicket";
29
28
  * The states no transition leaves, in every ticket workflow.
30
29
  *
31
30
  * The server's own definition (`TypeWorkflows::isTerminal` — "a state no
32
- * transition leaves") evaluates to exactly this pair for all three workflows.
31
+ * transition leaves") evaluates to exactly this pair for `bb_work`.
33
32
  */
34
33
  export declare const TERMINAL_TICKET_STATES: ReadonlySet<string>;
35
34
  /** The option lists the popup offers (loaded by `loadEditFormOptions`). */
package/dist/src/Entity/ticket/Form/edit.js CHANGED
@@ -21,11 +21,10 @@ import { PARENT_PAGE_SIZE } from '../Data/parents.js';
21
21
  * `cancelled`, so no served fact carries the cancel edge. The precedent is
22
22
  * `STATE_FILTER_VALUES` in `Data/query.ts`, hardcoded for the same reason.
23
23
  *
24
- * One constant serves every ticket workflow because in ALL of them
25
- * (`bb_work`, `bb_deployment`, `bb_verification`) `cancel.from` is exactly
26
- * the set of non-terminal states — so "non-terminal" and "the workflow permits
27
- * cancelling" are the same predicate, and no workflow id is needed to tell
28
- * them apart.
24
+ * One constant serves every ticket workflow because in the ticket workflow
25
+ * (`bb_work`) `cancel.from` is exactly the set of non-terminal states — so
26
+ * "non-terminal" and "the workflow permits cancelling" are the same
27
+ * predicate, and no workflow id is needed to tell them apart.
29
28
  */
30
29
  export const CANCELLED_STATE = 'cancelled';
31
30
  /**
@@ -39,7 +38,7 @@ export const CANCEL_TICKET_ACTION_ID = 'cancelTicket';
39
38
  * The states no transition leaves, in every ticket workflow.
40
39
  *
41
40
  * The server's own definition (`TypeWorkflows::isTerminal` — "a state no
42
- * transition leaves") evaluates to exactly this pair for all three workflows.
41
+ * transition leaves") evaluates to exactly this pair for `bb_work`.
43
42
  */
44
43
  export const TERMINAL_TICKET_STATES = new Set([
45
44
  'done',
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@bakers-build/addon-bakers-ui",
3
- "version": "0.1.2-next.194",
3
+ "version": "0.1.2-next.206",
4
4
  "description": "bakers.build TUI: interactive terminal UI (dashboard, projects, tickets) as a dropsh `tui` renderer plugin.",
5
5
  "type": "module",
6
6
  "license": "MIT",
@@ -29,7 +29,7 @@
29
29
  "zustand": "^5.0.15"
30
30
  },
31
31
  "peerDependencies": {
32
- "@bakers-build/core": "^0.1.2-next.194",
33
- "@bakers-build/message": "^0.1.2-next.194"
32
+ "@bakers-build/core": "^0.1.2-next.206",
33
+ "@bakers-build/message": "^0.1.2-next.206"
34
34
  }
35
35
  }