FLAT
CouperSevenval TechnologiesDocker ImageGithub
master
master
  • Changelog
  • FLAT
  • Administration
    • Configuration
    • Docker
    • Logging
  • Cookbook
    • Using the Built-in Mocking
    • Performing Additional Checks on JWT Access Tokens
    • Logging Custom Fields
    • Using Environment Variables
    • Handling Errors with an Error Flow
    • File Serving
    • Forwarding a Request to an Upstream API
    • Extracting Common Initialization Flow Tasks
    • Encoding and Decoding JWT
    • Passing Header Fields to the Client
    • How can I pass an arbitrary header field to an upstream system?
    • Performing Additional Checks on JWT Access Tokens
    • Proxying requests to Upstream APIs
    • Increasing the Request Timeout
    • How can I see what the client requested?
    • Using Swagger UI for API Documentation
    • Testing API Requests
    • Testing with Backend Requests
    • Testing Templates
    • Sending POST Requests
    • Processing Upstream Responses
    • Protecting Access using JWT Tokens
  • Reference
    • Configuration
    • Debugging
    • flat CLI
    • Flow
    • Variables
    • OpenAPI / Swagger Integration
    • OpenAPI
      • CORS - Cross-Origin Resource Sharing
    • OpenAPI
      • Differences from Swagger
    • OpenAPI
      • Mocking
    • OpenAPI
      • Routing
    • OpenAPI
      • Security
    • OpenAPI
      • Upstream APIs
    • OpenAPI
      • Validation
    • Flow Actions
      • assert Action
      • auth Action
      • backend-flow Action
      • copy Action
      • debug Action
      • dump Action
      • echo Action
      • error Action
      • eval Action
      • log Action
      • nameshave Action
      • pass-body Action
      • proxy-request Action
      • regex Action
      • request Action
      • requests Action
      • serve Action
      • set-config Action
      • set-env Action
      • set-response-headers Action
      • set-status Action
      • sub-flow Action
      • template Action
      • test-request Action
      • xslt Action
    • Functions
      • apply-codecs()
      • array-reverse()
      • array()
      • base64-decode()
      • base64-encode()
      • body()
      • calc-signature()
      • capitalize-first()
      • content()
      • decrypt-xml()
      • decrypt()
      • encrypt()
      • ends-with()
      • file-exists()
      • fit-document()
      • fit-log()
      • fit-serialize()
      • get-log()
      • has-class()
      • html-parse()
      • join()
      • json-doc()
      • json-parse()
      • json-stringify()
      • json-to-csv()
      • json-to-xml()
      • jwt-decode()
      • jwt-encode()
      • ldap-lookup()
      • ldap-query()
      • lookup()
      • matches()
      • md5()
      • replace()
      • sort()
      • split()
      • tolower()
      • toupper()
      • trim()
      • unixtime()
      • urldecode(), url-decode()
      • urlencode(), url-encode()
      • uuid3() and uuid4()
      • verify-signature()
      • verify-xmldsig()
      • xml-parse()
      • xml-to-json()
    • Templating
      • {{,}}
      • Comment {{// …}}
      • Dot {{.}}
      • Conditional `{{if <condition>}} … {{elseif <condition> }} … {{else}} … {{end}}
      • loop
      • ?? Operator
      • Object XML Notation (OXN)
      • Pair Producer {{: …}}
      • Placeholder
      • Template Variables
      • with
    • Testing
  • Tutorial
Powered by GitBook
On this page

Was this helpful?

  1. Reference
  2. Templating

loop

Input:

{
  "list": [
    1,
    2,
    3
  ]
}

Template:

<template>
{
  "numbers": [
    {{loop list}}
      {{ . }}
    {{end}}
  ]
}
</template>

Output:

{
  "numbers": [
    1,
    2,
    3
  ]
}

The loop command iterates over arrays. The expression given must therefore return an array for the loop body to be executed. The loop body is invoked once for each element in the array. For each invocation, the context . will be set to the current element of the array.

In the above example, we did not explicitly place a comma in the loop body. However, JSON requires a comma to separate array values or pairs in objects. Therefore, the loop command automatically produces commas to separate its child productions.

You may also use a literal comma at the end of the loop body. This will not result in duplicate commas. However, as a literal comma is produced as part of each iteration, the last production will end with that comma. This may result in invalid JSON if the surrounding array or object ends after the loop.

Example: loop over non-JSON data

Input:

<html>
<body>
<ul id="list" foo="bar">
  <li>One</li>
  <li>Two</li>
  <li>Three</li>
</ul>
</body>
</html>

Template:

<template>
[
  {{loop array(/html/body/ul/li)}}
    {{.}}
  {{end}}
]
</template>

Output:

[
  "One",
  "Two",
  "Three"
]

Attributes passed to the array() function will be converted to elements with the attribute's name in its name attribute, and the value of the attribute as its content. This can be used to iterate over lists of attributes:

Template (identical input as above):

<template>
{
  {{loop array(//ul/@*)}}
    {{ @name }}: {{.}}
  {{end}}
}
</template>

Output:

{
  "id": "list",
  "foo": "bar"
}
PreviousConditional `{{if <condition>}} … {{elseif <condition> }} … {{else}} … {{end}}Next?? Operator

Last updated 5 years ago

Was this helpful?

If the data to be used in a loop is not a JSON array, the can be used to convert the data:

array() function