Index of every page on this site: llms.txt
All skills
langflow-ai avatar

/frontend-query-mutation

@21381e5
by Langflowlangflow-ai/langflow157k stars
10,435
Run it yourself

Guide for implementing Langflow frontend query and mutation patterns with Axios and TanStack React Query v5. Trigger when creating or updating API hooks in controllers/API/queries, consuming UseRequestProcessor in components, deciding whether to use useQuery or useMutation, handling conditional queries, cache invalidation, mutation error handling, or migrating legacy API calls to the query hook pattern.

Use this Skill: https://skilld.dev/gh/langflow-ai/langflow/frontend-query-mutation

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈108 tokens for metadata: the name and description. ≈864 when used: this file. ≈6.4k more on demand in 2 files.

Description uses 5.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈432 characters, or 5.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Frontend Query & Mutation

Intent

  • Keep API hooks in controllers/API/queries/{domain}/ as the organized source of truth.
  • Use UseRequestProcessor for consistent retry, invalidation, and error handling.
  • Use Axios api instance for all HTTP calls (never raw fetch for REST).
  • Use performStreamingRequest() for streaming operations (build, chat).
  • Keep cache invalidation in mutation onSettled callbacks.

Architecture Overview

Langflow uses Axios + TanStack React Query v5 for data fetching. There is no oRPC or contract layer. The architecture is:

Component
  -> API hook (controllers/API/queries/{domain}/use-{verb}-{resource}.ts)
    -> UseRequestProcessor (controllers/API/services/request-processor.ts)
      -> useQuery / useMutation (TanStack React Query)
        -> queryFn / mutationFn
          -> api.get/post/patch/delete (Axios instance from controllers/API/api.tsx)

Key Files

File Purpose
controllers/API/api.tsx Axios instance, ApiInterceptor component, performStreamingRequest()
controllers/API/services/request-processor.ts UseRequestProcessor hook wrapping useQuery/useMutation with retry defaults
controllers/API/helpers/constants.ts URL constants (URLs) and getURL() helper
controllers/API/queries/{domain}/ Domain-organized query and mutation hooks
types/api/index.ts useQueryFunctionType, useMutationFunctionType type helpers
stores/ Zustand stores for client-side state

Workflow

  1. Identify the change surface.
    • Read references/query-patterns.md for hook structure, naming, URL patterns, and query/mutation call-site shape.
    • Read references/runtime-rules.md for conditional queries, invalidation, error handling, and streaming.
    • Read both references when a task spans hook creation and runtime behavior.
  2. Implement the hook following existing patterns.
    • Use UseRequestProcessor for query() and mutate() wrappers.
    • Use the api Axios instance for all HTTP calls.
    • Use getURL() for constructing API paths.
    • Type the hook with useQueryFunctionType or useMutationFunctionType.
  3. Preserve Langflow conventions.
    • Query keys are arrays with the hook name: ["useGetFlows"].
    • Mutations invalidate related queries in onSettled.
    • Zustand store updates happen in the query/mutation function, not in components.
    • UseRequestProcessor provides default retry (5 for queries, 3 for mutations) with exponential backoff.

Files Commonly Touched

  • controllers/API/queries/{domain}/use-get-*.ts (query hooks)
  • controllers/API/queries/{domain}/use-post-*.ts (create mutations)
  • controllers/API/queries/{domain}/use-patch-*.ts (update mutations)
  • controllers/API/queries/{domain}/use-delete-*.ts (delete mutations)
  • controllers/API/helpers/constants.ts (URL constants)
  • types/api/index.ts (API type definitions)
  • stores/ (Zustand store updates triggered by queries)

References

  • Use references/query-patterns.md for hook structure, naming conventions, directory layout, and anti-patterns.
  • Use references/runtime-rules.md for conditional queries, invalidation, mutate versus mutateAsync, error handling, and streaming requests.

Treat this skill as the single query and mutation entry point for Langflow frontend work. Keep detailed rules in the reference files instead of duplicating them in project docs.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo4 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides architectural guidelines and code templates for frontend development in the Langflow project. It documents best practices for using Axios and TanStack React Query. No security issues were detected.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 21381e5. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated 8 months ago

README badge

README badge for langflow-ai/langflow/frontend-query-mutation