跳到正文
cccskills
免费在 GitHub 公开

frontend-api

Frontend API integration — generated SDK, apiCallWithLoading, blockUi, wrapped responses, toOpenApiError. Use when calling the generated backend API from the frontend.

中文简介正在准备中。当前显示原文说明。

nerds-odd-e/doughnut星标 50(GitHub 50 + cccskills 0)

实测评分 未实测

查看安装方法

包含的文件(1)

  • SKILL.md4.7 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Frontend API Rules

API Integration

  • Import services from @generated/donut-backend-api/sdk.gen.
  • Wrapped response: { data, error, request, response }.
  • User-initiated actions: apiCallWithLoading (loading bar + error toasts).
  • Direct SDK calls are silent: no loading bar and no error toasts.
import { UserController } from "@generated/donut-backend-api/sdk.gen"
import { apiCallWithLoading } from "@/managedApi/clientSetup"

const { data: newUser, error } = await apiCallWithLoading(() =>
  UserController.createUser({ body: formData })
)

const { data: users, error: loadError } = await UserController.getUserProfile()

Loading indicators

apiCallWithLoading drives two global surfaces from DonutApp.vue:

  • Thin loading bar — any wrapped call in flight.
  • Whole-UI blocking modal — { blockUi: true }. Native <dialog showModal()>, so it paints above other top-layer dialogs.

Use { blockUi: true, message?: string } when the rest of the UI must wait (view transition, or a mutation where partial interaction would confuse state). Show the blocker only after any confirmation. Do not add component-local LoadingModal refs.

const { data, error } = await apiCallWithLoading(
  () => AssimilationController.next({ query: { timezone: timezoneParam() } }),
  { blockUi: true, message: "Loading next note..." }
)

Keep local loading (inline spinner, disabled control) when the user should still use the rest of the page. Those calls can still use apiCallWithLoading without blockUi.

Cancelable blocking calls

For safe read-only blockers, pass { blockUi: true, cancelable: true, message?: string }. Returns CancelableApiResult<T> ({ status: "completed"; result } | { status: "cancelled" }). Narrow on status before using result; do not treat cancel as an API error.

const outcome = await apiCallWithLoading(
  (signal) =>
    AiController.generateRefinementSuggestions({
      path: { note: noteId },
      signal,
    }),
  {
    blockUi: true,
    cancelable: true,
    message: "AI is generating refinement layout...",
  }
)

if (outcome.status === "cancelled") {
  return
}

const { data, error } = outcome.result

Accepted cancel is silent (no toast). Abort is client-only. Do not opt mutations or irreversible writes into cancelable: true. Do not invent AbortError-name matching or a cancelable runWithBlockingApiLoading.

cancelable: true is allowlisted in frontend/tests/managedApi/cancelableAllowlist.spec.ts (ALLOWED_CANCELABLE_FILES). Add a site there when introducing a new cancelable call; do not add cancelable: true outside that set.

For one continuous blocker across multiple calls, wrap them in runWithBlockingApiLoading(operation, message) (noncancelable). Inner apiCallWithLoading calls keep thin bar + toasts only.

Blocking classification

Every new { blockUi: true } or runWithBlockingApiLoading site is cancelable, intentionally noncancelable, or nonblocking. Classify it; do not leave it unclassified.

  • Cancelable — only allowlisted read-only opt-ins (cancelableAllowlist.spec.ts).
  • Intentionally noncancelable — mutations, view transitions that must finish, AI reads with no defined post-cancel UX.
  • Nonblocking — thin-bar apiCallWithLoading without blockUi, or a direct SDK call.

Loading UI that means unfinished work marks data-app-busy (LoadingThinBar, ContentLoader, LoadingModal; gated by frontend/tests/components/commons/AppBusyMarker.contract.spec.ts). E2E: waitUntilAppIsNotBusy() from e2e_test/start/pageBase.ts. The wait means busy UI cleared, not success.

API Return Value Usage

The global client uses responseStyle: "fields" and throwOnError: false.

  1. Destructure with meaningful names: const { data: updatedUser, error } = await updateUser(...).
  2. Check !error before using data; no separate data check.
  3. When error is undefined, TypeScript types data as the success shape.
  4. Do not add runtime property checks for required typed properties.
  5. Do not add else if (data) after checking error.

Validation Errors

For 400 field errors, toOpenApiError(error) ({ errors?: Record<string, string>; message?: string }). apiCallWithLoading already toasts; extract errors only for form fields.

import { toOpenApiError } from "@/managedApi/openApiError"

if (error) {
  errors.value = toOpenApiError(error).errors || {}
} else {
  errors.value = {}
  user.value = updatedUser
}

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

backend

免费

Backend Java — Spring Boot controllers/services, JUnit controller tests, MakeMe. Read this first for any backend work. Use when working on the Java Spring backend.

中文简介正在准备中。当前显示原文说明。

nerds-odd-e/doughnut502026年10月26日 更新

Backend Java production code, Spring Boot controllers/services/repositories, controller return values, imports, schema ERD pointer. Use when editing backend production Java.

中文简介正在准备中。当前显示原文说明。

nerds-odd-e/doughnut502026年10月26日 更新

Backend Java tests, controller-level stable-boundary tests, JUnit, @Nested, MakeMe builders, @Transactional, parameterized tests. Use when writing or changing backend JUnit tests.

中文简介正在准备中。当前显示原文说明。

nerds-odd-e/doughnut502026年10月26日 更新

cli

免费

related to donut CLI. Use when working on donut-cli.

中文简介正在准备中。当前显示原文说明。

nerds-odd-e/doughnut502026年10月26日 更新

Set up and run the Donut dev environment on Cursor Cloud VM (no Nix). Use when working on Cloud VM, running tests on Cloud VM, or encountering command errors related to missing nix. Triggers on: cloud VM, cloud agent, no nix available, /workspace path.

中文简介正在准备中。当前显示原文说明。

nerds-odd-e/doughnut502026年10月26日 更新

Regenerate docs/database-erd.md from MySQL information_schema (Mermaid ERD: foreign keys and key columns). Use after Flyway schema changes, new migrations, or when the diagram is stale. Triggers on: database ERD, database-erd.md, export_database_erd, schema diagram, ER diagram after migration.

中文简介正在准备中。当前显示原文说明。

nerds-odd-e/doughnut502026年10月26日 更新

查看 nerds-odd-e 的全部技能

报告此技能的问题