v1.3.0

⚠️ This release is potentially disruptive. Initialize will throw for previously ignored problems with configuration
correctness. The coalesce logic for using multiple configuration sources has changed. For details see
Layered Configuration.

Changed

• core: initialization throws if mandatory configuration fallbackValue is undefined (missing) or null (always
  invalid).

• core: initialization throws if mandatory configuration type is not in ["boolean", "number", "string"] (invalid).

• core: initialization throws if its invoked more than once. previously subsequent calls and their options were
  ignored.

• core: configuration reading and coalescing has changed:

  • up to v1.2.5, the order was runtime, files, auto, where the first occurrence is used for each toggle
  • from v1.3.0, the order is auto, files, runtime, where the last occurrence is used for each toggle
  • this enables overriding the configuration based on environmental factors, by mixing in dedicated config files