fix: re-export CustomValidationRule and expose validation arguments

[josh-padnick]

Description

After #277, external consumers (e.g., Gruntwork Runbooks) that use boilerplate as a Go library can no longer reference CustomValidationRule by name after the move to internal/. They also lack a way to extract validation arguments (e.g. The 1, 3 in length(1, 3)) using the Go interfaces available through boilerplate. These changes restore public API access and provide structured metadata for parameterized validation rules.

Details

• Re-export CustomValidationRule from the variables package via a type alias, restoring public access that was lost when feat: Adding WASM build target #277 moved the type to internal/validation
• Add an Args field to CustomValidationRule so that parameterized rules (regex, length) expose their arguments programmatically
• Update the WASM stub struct to include the new field

TODOs

Read the Gruntwork contribution guidelines.

• Update the docs.
• Run the relevant tests successfully, including pre-commit checks.
• Ensure any 3rd party code adheres with our license policy or delete this line if its not applicable.
• Include release notes. If this PR is backward incompatible, include a migration guide.

Release Notes (draft)

fix: re-export CustomValidationRule and expose validation arguments

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
boilerplate	Ready	Preview, Comment	Feb 24, 2026 1:02am