fix: accept unresolved references in schema_validation

[ameyypawar]

Summary

When a script enables // schema_validation and has a parameter typed as a resource (or any object), executing it with that parameter supplied as a Windmill reference fails:

Argument `gmail` should be an object

Schema validation runs before the worker resolves references, so a $res:… (or $var:/$jsonvar:/$encrypted:) reference is still a string at validation time and is rejected by the object rule.

Changes

• windmill-common/src/schema.rs: SchemaValidationRule::apply_rule now short-circuits when the value is an unresolved reference string ($var:/$jsonvar:/$res:/$encrypted: — the prefixes the worker resolves), accepting it regardless of the declared type. The worker resolves the reference to its real value after validation runs.
• Add a regression test (validate_accepts_unresolved_reference_for_object_param) covering all four reference prefixes, a genuine object (still validates), and a plain non-reference string (still rejected).

Test plan

• cargo test -p windmill-common validate_accepts_unresolved_reference_for_object_param
• Deploy the issue's repro (a // schema_validation script with a resource parameter) and run it with the resource selected; confirm no "should be an object" error.

Fixes #6938

---

Summary by cubic

Allow unresolved Windmill references during schema validation so object/resource params passed as $res:/$var:/$jsonvar:/$encrypted: no longer fail with "should be an object". The worker resolves these after validation. Fixes #6938.

• Bug Fixes
  • Short-circuit SchemaValidationRule::apply_rule to accept $var:, $jsonvar:, $res:, $encrypted: strings for any declared type.
  • Added a regression test covering all four prefixes, a valid object, and rejecting a plain non-reference string.

^{Written for commit 5752869. Summary will update on new commits.}

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}