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

Pair Producer {{: …}}

The pair producer {{: expression_selecting_keys }} creates key-value pairs. It should only be used in a context where key-value pairs are allowed (i.e. in a JSON object context).

The expression following the colon (':') is evaluated and the result is used as a list of keys. All key-value pairs in the current context with a matching key in this list of keys are copied to the output.

Note: With markup input, you can only select element or attribute nodes, because other node types don't have a name (see "Example: XML input").

The pair producer also creates commas between and after its pairs. Therefore you should avoid placing an explicit comma behind a pair producer. If an expression does not match anything, no output would be produced. In that case, your literal comma could be illegal.

Example: explicit keys

Input:

{
  "foo": 1,
  "bar": [{"key":"value"}],
  "baz": 3
}

Template:

{
  {{: foo | bar }}
}

Output:

{
  "foo": 1,
  "bar": [{"key":"value"}]
}

Example: filter

Input:

{
  "foo": 1,
  "bar": 2,
  "ba z": {"key":"value"}
}

Template:

{
  {{: *[not(name() = 'bar')] }}
}

Output:

{
  "foo": 1,
  "ba z": {"key":"value"}
}

Example: automatic comma

Input:

{
  "foo": 1,
  "bar": 2,
  "baz": 3
}

Template:

{
  {{: * }}
  "add": "this"
}

Output:

{
  "foo": 1,
  "bar": 2,
  "baz": 3,
  "add": "this"
}

Example: XML input

Input:

<root foo="1">
  <bar>2</bar>
  <baz>3</baz>
  <!-- a comment -->
</foo>

Template:

{
  {{: @foo | //bar | //baz/text() | //comment() }}
}

Output:

{
  "foo": 1,
  "bar": 2
}
PreviousObject XML Notation (OXN)NextPlaceholder

Last updated 5 years ago

Was this helpful?