@checkstack/frontend-api 0.5.1 → 0.6.0

package/CHANGELOG.md

@@ -1,5 +1,107 @@
 # @checkstack/frontend-api
 
+## 0.6.0
+
+### Minor Changes
+
+- e2d6f25: feat(automation): connection picker for integration actions + restore Integrations menu
+
+  Connection-backed automation actions (Jira, Teams, Webex) now render a
+  working connection picker plus cascading provider dropdowns in the
+  visual editor, and the Integrations entry is back in the user menu.
+
+  **Contract.** `ActionDefinition` gained an optional
+  `connectionProviderId` (and it is surfaced on `ActionInfoSchema` and
+  mapped in the `listActions` router). It carries the integration
+  provider's fully-qualified id, derived from the provider plugin's own
+  `pluginMetadata.pluginId` (never a hardcoded string), so the editor
+  knows which provider backs an action's dropdowns and it matches the
+  `qualifiedId` the integration provider registry assigns.
+
+  **Providers.** Jira, Teams and Webex each export
+  `*_PROVIDER_LOCAL_ID` / `*_PROVIDER_QUALIFIED_ID`, register their
+  provider with the local id, and add a `CONNECTION_OPTIONS`
+  (`"connectionOptions"`) resolver name. Their `post_message` /
+  issue actions set `connectionProviderId` and expose `connectionId`
+  as an `x-options-resolver` dropdown instead of a hidden field.
+
+  **Frontend bridge.** A new `useConnectionOptionResolvers` hook
+  (`@checkstack/automation-frontend`, which now depends on
+  `@checkstack/integration-common`) turns an action's
+  `x-options-resolver` schema fields into live data: the
+  `connectionOptions` resolver lists the provider's connections via
+  `listConnections`, and every other resolver name is forwarded to
+  `getConnectionOptions` for the selected `connectionId`, passing the
+  live form values as `context` for dependent fields. `ProviderActionBody`
+  now passes this map to `DynamicForm` (it was previously missing
+  entirely, so connection-backed actions had no working dropdowns).
+
+  **frontend-api.** `usePluginClient` procedures now also expose a typed
+  imperative `.call(input)` alongside `.useQuery` / `.useMutation`, for
+  async callbacks that cannot host a hook (such as a `DynamicForm`
+  options resolver). Additive, non-breaking.
+
+  **Integrations menu.** Re-added `IntegrationMenuItem` and a new
+  `IntegrationsLandingPage`, wired into `integration-frontend` as a list
+  route and a `UserMenuItemsSlot` entry under the "Configuration" group.
+
+  **Action card polish.** The action editor's secondary metadata (id,
+  description, failure behaviour) is now grouped into one quiet settings
+  panel with consistent small uppercase "eyebrow" labels, so the action's
+  own configuration stays the focal point. The raw failure checkbox was
+  replaced with the standard `Checkbox` control, and the provider action
+  picker / configuration sections gained consistent section headers and a
+  divider. The per-step "type" dropdown was removed: an action's kind is
+  fixed at creation, so changing it now means adding a new step and
+  deleting the old one (avoids the surprising full-config reset that
+  switching kinds used to trigger).
+
+  **Add-step picker.** Adding a step now opens a Home-Assistant-style
+  dialog where the operator decides the step type up front: an "Actions"
+  tab lists the registered provider actions grouped by category
+  (searchable; picking one presets the step's `action`), and a "Blocks"
+  tab lists the structural building blocks (choose / parallel / repeat /
+  etc.). Because the concrete action is chosen here, the in-card action
+  switcher was removed - a step's action is fixed once created. Composite
+  blocks now start with an empty child list (filled via the nested
+  add-step picker) instead of seeding an unconfigurable empty action.
+
+### Patch Changes
+
+- Updated dependencies [6d52276]
+  - @checkstack/common@0.12.0
+  - @checkstack/signal-common@0.2.5
+
+## 0.5.2
+
+### Patch Changes
+
+- f23f3c9: Establish the canonical optimistic-UI pattern for oRPC mutations
+  (`onMutate` snapshot / patch, `onError` rollback, `onSettled`
+  invalidate) and apply it to the two highest-frequency toggles where
+  perceived latency was most visible:
+
+  - `markAsRead` on the Notifications page — clicking the check on a
+    notification card now flips the read state immediately instead of
+    waiting for the round-trip.
+  - `pauseConfiguration` / `resumeConfiguration` on the Health Check
+    Config page — pause/resume now flip the row's badge instantly,
+    rolling back on server error.
+
+  The wrapper type for `useMutation` on each plugin client gained an
+  optional `TContext` generic so optimistic sites can return a snapshot
+  from `onMutate` and consume it in `onError` without `unknown` casts.
+  The runtime behaviour and the auto-invalidation on success are
+  unchanged; the change is additive on the type surface only.
+
+  Full pattern and "when NOT to use it" guidance live in
+  `docs/frontend/optimistic-updates.md`.
+
+- Updated dependencies [f23f3c9]
+- Updated dependencies [f23f3c9]
+  - @checkstack/common@0.11.0
+  - @checkstack/signal-common@0.2.4
+
 ## 0.5.1
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@checkstack/frontend-api",
-  "version": "0.5.1",
+  "version": "0.6.0",
   "license": "Elastic-2.0",
   "type": "module",
   "main": "./src/index.ts",
@@ -13,8 +13,8 @@
     "react": "^18.0.0"
   },
   "dependencies": {
-    "@checkstack/common": "0.9.0",
-    "@checkstack/signal-common": "0.2.2",
+    "@checkstack/common": "0.11.0",
+    "@checkstack/signal-common": "0.2.4",
     "@orpc/client": "^1.13.14",
     "@orpc/contract": "^1.13.14",
     "@orpc/react-query": "1.13.4",
@@ -26,7 +26,7 @@
     "@types/react": "^18.0.0",
     "typescript": "^5.0.0",
     "@checkstack/tsconfig": "0.0.7",
-    "@checkstack/scripts": "0.3.1"
+    "@checkstack/scripts": "0.3.3"
   },
   "checkstack": {
     "type": "tooling"

package/src/orpc-query.tsx

@@ -89,19 +89,36 @@ interface QueryProcedure<TInput, TOutput> {
     input?: TInput,
     options?: Omit<UseQueryOptions<TOutput, Error>, "queryKey" | "queryFn">,
   ) => UseQueryResult<TOutput, Error>;
+  /**
+   * Imperative one-shot call, outside React Query. Use inside async
+   * callbacks that can't host a hook (e.g. a DynamicForm options
+   * resolver). Prefer `useQuery` for anything rendered.
+   */
+  call: (input: TInput) => Promise<TOutput>;
 }
 
 /**
  * Mutation procedure hook interface - only exposes useMutation.
  * Mutations don't take input directly - it's passed to mutate/mutateAsync.
+ *
+ * `TContext` is threaded through the options so optimistic-update sites
+ * can return a snapshot from `onMutate` and read it back in `onError`
+ * without resorting to `unknown` casts. See
+ * `docs/frontend/optimistic-updates.md` for the canonical pattern.
  */
 interface MutationProcedure<TInput, TOutput> {
-  useMutation: (
+  useMutation: <TContext = unknown>(
     options?: Omit<
-      UseMutationOptions<TOutput, Error, TInput>,
+      UseMutationOptions<TOutput, Error, TInput, TContext>,
       "mutationFn" | "mutationKey"
     >,
-  ) => UseMutationResult<TOutput, Error, TInput>;
+  ) => UseMutationResult<TOutput, Error, TInput, TContext>;
+  /**
+   * Imperative one-shot call, outside React Query. Use inside async
+   * callbacks that can't host a hook (e.g. a DynamicForm options
+   * resolver). Prefer `useMutation` for anything tied to UI lifecycle.
+   */
+  call: (input: TInput) => Promise<TOutput>;
 }
 
 /**
@@ -350,6 +367,7 @@ function createProcedureHook<TInput, TOutput>(
         const { onSuccess: _, ...restOptions } = options ?? {};
         return useMutation({ ...mutationOpts, ...restOptions });
       },
+      call: (input) => proc.call(input),
     };
   }
 
@@ -362,5 +380,6 @@ function createProcedureHook<TInput, TOutput>(
       // Spread caller options AFTER to ensure they take precedence (e.g., enabled: false)
       return useQuery({ ...queryOpts, ...options });
     },
+    call: (input) => proc.call(input),
   };
 }