hasura/graphql-engine · info · ArgumentSource
command '{0}'
Error message
command '{0}' What it means
Not a standalone error: it is the Display formatting for ArgumentSource::Command, rendering 'command '<name>''. It appears only as context inside larger error messages produced by the arguments resolution stage, identifying that the failing argument belongs to a command rather than a model.
Source
Thrown at v3/crates/metadata-resolve/src/stages/arguments/types.rs:17
use std::collections::BTreeMap;
use crate::stages::boolean_expressions;
use crate::types::error::ContextualError;
use crate::types::subgraph::ArgumentKind;
use crate::{Qualified, QualifiedTypeReference};
use indexmap::IndexMap;
use open_dds::arguments::ArgumentName;
use open_dds::commands::CommandName;
use open_dds::models::ModelName;
use serde::{Deserialize, Serialize};
#[derive(Debug, Clone, thiserror::Error, Eq, Ord, PartialEq, PartialOrd)]
pub enum ArgumentSource {
#[error("model '{0}'")]
Model(Qualified<ModelName>),
#[error("command '{0}'")]
Command(Qualified<CommandName>),
}
pub struct ArgumentsOutput {
pub arguments: BTreeMap<ArgumentSource, IndexMap<ArgumentName, ArgumentInfo>>,
pub issues: Vec<ArgumentIssue>,
}
#[derive(Serialize, Deserialize, Clone, Debug, PartialEq, Eq)]
pub struct ArgumentInfo {
pub argument_type: QualifiedTypeReference,
pub description: Option<String>,
pub argument_kind: ArgumentKind,
pub type_representation: Option<ndc_models::TypeRepresentation>,
}
#[derive(Debug, Clone, thiserror::Error)]
pub enum ArgumentIssue {View on GitHub (pinned to 724551b9ae)
Solutions
- Read the rest of the error message: the actual failure is attached after 'command '...''
- Fix the command's argument definition in its OpenDD YAML (usually the argumentType)
- Rebuild and confirm the command resolves
Defensive patterns
Strategy: try-catch
Try / catch
// Handle the wrapping error; use the 'command '...'' name to jump to the command's OpenDD definition and fix its argumentType.
Prevention
- Read the full error line: the actionable failure follows the 'command '...'' prefix
- Keep command argument types aligned with boolean expression type definitions
When it happens
Trigger: Surfaced when an argument defined on an OpenDD command has an issue (e.g. its boolean expression type fails to resolve) and the ArgumentSource is formatted into the error output.
Common situations: Command arguments whose argumentType references a broken boolean expression type; the prefix points you at the specific command in the metadata to fix.
Related errors
- model '{0}'
- Unknown type: {type_name}
- argument {argument_name:?} has an issue: {issue:?}
- unknown type '{type_name}' used in object boolean expression
- unsupported type '{type_name}' used in object boolean expres
AI-assisted analysis of hasura/graphql-engine@724551b9ae (2026-08-28).
Data as JSON: /api/errors/72450bd86b040e34.
Report an issue: GitHub.