The Iterator: Matrix Comprehensions
Traverse and transform collections of ward configurations without exposing underlying representations.
package wards
// Raw Data Collection
#RawData: {
"zone-A": 100
"zone-B": 45
"zone-C": 300
}
// The Iterator/Processor Matrix
#EnergyNormalizer: {
input: [string]: int
// Iterating over the map to produce a list of standardized ward configs
// We use CUE's list comprehension as our Iterator mechanism
output: [
for zone, energy in input {
{
id: zone
power: energy
// Transformation logic during iteration
status: (energy >= 100) ? "ACTIVE" : "STANDBY"
}
}
]
}
// Usage
process_wards: #EnergyNormalizer & {
input: #RawData
}
active_manifest: process_wards.output
In traditional languages, an Iterator is an object with a .next() method. In the static, declarative world of CUE, iteration is handled exclusively through comprehensions (for ... in).
When dealing with arrays or maps of Lattice Data Validation Wards, you need a safe way to traverse and map data into new structural states without writing procedural loops. The #EnergyNormalizer acts as a data-transformation iterator. It takes an arbitrary input map, iterates over every key-value pair, applies threshold logic ((energy >= 100) ? "ACTIVE" : "STANDBY"), and projects an entirely new structured output list, fully validated against the unified graph.