3fb4ed0d92
In normal situations the block type name alone is enough to determine the appropriate schema for a child, but when callers are otherwise doing unusual pre-processing of bodies to dynamically generate schemas during decoding they are likely to need to take similar steps while analyzing for variables, to ensure that all of the references can be located in spite of the not-yet-applied pre-processing. |
||
|---|---|---|
| .. | ||
| dynblock | ||
| include | ||
| transform | ||
| typeexpr | ||
| userfunc | ||
| README.md | ||
HCL Extensions
This directory contains some packages implementing some extensions to HCL
that add features by building on the core API in the main hcl package.
These serve as optional language extensions for use-cases that are limited only to specific callers. Generally these make the language more expressive at the expense of increased dynamic behavior that may be undesirable for applications that need to impose more rigid structure on configuration.