Adding conditions in your configuration

Conditions in Configuration

Some of the config properties can be defined by using conditions.

These are the most used conditions: 

• amount()
• paymentMethod()
• paymentType()
• recurringInterval()
• purpose()
• currency().

A condition dynamically gets a value from the widget and based on the resulting value you can for instance either show or hide some of elements of the widget.

As an example - let's override the payment methods. Three payment methods will be shown: Credit Card,  PostFinance and SMS. The latter will only be shown when the following condition evaluates to true: If selected amount is greater than 100, SMS method will be hidden otherwise it will be shown. Check out the full example:

<script>
  window.rnw.tamaro.runWidget('.rnw-widget-container', {
    paymentMethods: [
      "eca",
      "vis",
      "amx",
      "pfc",
      {
        "if": "amount() < 100",
        "then": "sms"
      },
    ]
  });
</script>

 That was easy, wasn't it?

Let's try the next one: Based on a selected purpose we want to have different payment methods available: The SMS payment method will only be shown when the first purpose is selected. The condition we will use for that is `purpose()`:

<script>
window.rnw.tamaro.runWidget('.rnw-widget-container', {
  paymentMethods: [
    "eca",
    "vis",
    "amx",
    "pfc",
    {
      "if": "purpose() == p1",
      "then": "sms"
    },
  ]
});
</script>

If you need to show different values of amounts based on the selected currency - use currency() in the condition as in the example below:

<script>
window.rnw.tamaro.runWidget('.rnw-widget-container', {

  currencies: [ "usd", "chf", "eur" ],

  amounts: [
    {
      "if": "currency() == usd",
      "then": [5,10,50,100],
    },
    {
      "if": "currency() == chf",
      "then": [10,15,60,80],
    },
    {
      "if": "currency() == eur",
      "then": [15,20,80,100],
    },
  ]
});
</script>

A condition usually consists of operators and methods. The character > is an operator.
There are many operators that you're already used to and some that might be new to you.
New operators can easily be added to the Compiler class.
Besides operators, there are methods. The `amount()` expression is a method.
Methods are simple functions that may, or may not, take arguments and return a value.
New methods can easily be added like this: 

rnw.tamaro.compiler.addMethods({
 date: () => new Date().toLocaleString()
})

You might write conditions either in traditional or functional format, for example,
traditional: 1 < 2 and 3 > 2,
functional: and(lt(1, 2), gt(3, 2)).

List of available operators:

List of available methods:

Configuration options

List of all available configuration options, based on the WidgetConfig class. Please be aware that in Javascript we use camelCase where as defined in YAML we use snake_case for the parameter names.

No matter what config formats you've used, widget will merge them all together using this priority: Runtime > JavaScript > YAML and create a new config object based on those three. It is accessible trough the widget instance `window['widget'].computedConfig`. Do not try to override any values on the `computedConfig` object, since your changes will be overwritten as soon as the the config recomputates, use `window['widget'].config` instead. Be aware that config does not support a deep merge. So if you overwrite an object within the config, you have to provide the whole sub config of this object.