Rust Backend

windmill-labs/windmill/.agents/skills/rust-backend

作者 windmill-labsfb22e5ce368eba9146e0d51b8fdabb52ca9f68f0无许可证收录于 2026年10月9日更新于 2026年10月9日

Rust coding guidelines for the Windmill backend. MUST use when writing or modifying Rust code in the backend directory.

AI 生成的概览

面向 Windmill 后端的 Rust 编码规范,涵盖错误处理、SQLx、异步、serde 与 Axum 模式。

功能
提供在 backend 目录下编写或修改 Rust 代码时使用的 Windmill 专属约定。内容包括错误类型与结果别名、SQLx 查询规则(如避免 SELECT *、使用批量操作)、JSON 与 serde 处理、异步与互斥锁使用建议、模块可见性以及 Axum 处理函数写法。还说明了功能遥测允许列表的行为,并建议使用 rust-analyzer 进行代码导航。
适用场景
在 Windmill 后端目录中编写或修改 Rust 代码时使用。适合需要遵循项目在错误处理、数据库访问、并发和 API 处理函数方面既有模式的贡献者。
运行要求
不包含脚本,仅为说明性指引。假定项目使用 Rust 及 sqlx、serde、tokio 和 Axum,并建议使用 rust-analyzer LSP 进行导航。

Windmill Rust Patterns

Apply these Windmill-specific patterns when writing Rust code in backend/.

Error Handling

Use Error from windmill_common::error. Return Result<T, Error> or JsonResult<T>:

rust
use windmill_common::error::{Error, Result};
pub async fn get_job(db: &DB, id: Uuid) -> Result<Job> {    sqlx::query_as!(Job, "SELECT id, workspace_id FROM v2_job WHERE id = $1", id)        .fetch_optional(db)        .await?        .ok_or_else(|| Error::NotFound("job not found".to_string()))?;}

Never panic in library code. Reserve .unwrap() for compile-time guarantees.

SQLx Patterns

Never use SELECT * — always list columns explicitly. Critical for backwards compatibility when workers lag behind API version:

rust
// Correctsqlx::query_as!(Job, "SELECT id, workspace_id, path FROM v2_job WHERE id = $1", id)
// Wrong — breaks when columns are addedsqlx::query_as!(Job, "SELECT * FROM v2_job WHERE id = $1", id)

Use batch operations to avoid N+1:

rust
// Preferred — single query with IN clausesqlx::query!("SELECT ... WHERE id = ANY($1)", &ids[..]).fetch_all(db).await?

Use transactions for multi-step operations. Parameterize all queries.

JSON Handling

Prefer Box<serde_json::value::RawValue> over serde_json::Value when storing/passing JSON without inspection:

rust
pub struct Job {    pub args: Option<Box<serde_json::value::RawValue>>,}

Only use serde_json::Value when you need to inspect or modify the JSON.

Serde Optimizations

rust
#[derive(Serialize, Deserialize)]pub struct Job {    #[serde(skip_serializing_if = "Option::is_none")]    pub parent_job: Option<Uuid>,    #[serde(skip_serializing_if = "Vec::is_empty")]    pub tags: Vec<String>,    #[serde(default)]    pub priority: i32,}

Async & Concurrency

Never block the async runtime. Use spawn_blocking for CPU-intensive work:

rust
let result = tokio::task::spawn_blocking(move || expensive_computation(&data)).await?;

Mutex selection: Prefer std::sync::Mutex (or parking_lot::Mutex) for data protection. Only use tokio::sync::Mutex when holding locks across .await points.

Use tokio::sync::mpsc (bounded) for channels. Avoid std::thread::sleep in async contexts.

Module Structure & Visibility

  • Use pub(crate) instead of pub when possible
  • Place new code in the appropriate crate based on functionality
  • API endpoints go in windmill-api/src/ organized by domain
  • Shared functionality goes in windmill-common/src/

Code Navigation

Always use rust-analyzer LSP for go-to-definition, find-references, and type info. Do not guess at module paths.

Feature Telemetry

FEATURE_USAGE_KINDS in windmill-api-workspaces/src/workspaces.rs is an allowlist: a (feature, kind) pair missing from it is dropped by valid_feature_usage_event with a bare continue — no error, and the route still returns 204. Adding a counter on the frontend without registering it here records nothing. See docs/feature-telemetry.md.

Axum Handlers

Destructure extractors directly in function signatures:

rust
async fn process_job(    Extension(db): Extension<DB>,    Path((workspace, job_id)): Path<(String, Uuid)>,    Query(pagination): Query<Pagination>,) -> Result<Json<Job>> { ... }

来源与署名

来源:windmill-labs/windmill位于.agents/skills/rust-backend提交fb22e5c

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架