scriptoriumadmin/fabro
1
0
Fork 0
mirror of https://github.com/fabro-sh/fabro.git synced 2026-10-07 03:00:29 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

docs: clarify run-create undefined variable handling

Browse source
This commit is contained in:
Bryan Helmkamp 2026-07-28 14:52:02 -04:00
parent 40372340c0
commit 0681d1e6ee
No known key found for this signature in database
1 changed files with 4 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
lib/components/fabro-workflow/src/transforms/variable_expansion.rs
View file

@ -19,11 +19,10 @@ use crate::static_reference::{
/// How the template-expansion pass should treat undefined input variables.
///
/// Neither validate nor run-create should fail just because the user has not
/// bound `{{ inputs.* }}` yet, so both render structurally. Run-create then
/// promotes the resulting warnings to errors itself, which keeps its hard-fail
/// behavior while still reporting every undefined variable in one pass rather
/// than aborting on the first.
/// Both validate and run-create render structurally so they can report every
/// unbound `{{ inputs.* }}` variable in one pass rather than aborting on the
/// first. Run-create then promotes the resulting warnings to errors, which
/// keeps its hard-fail behavior.
#[derive(Clone, Copy, Debug)]
pub enum RenderMode {
/// Undefined inputs abort the pass with a hard error. No production caller