Bixby Developer Center

We've added a new runtime flag, no-filtering-with-validation, which changes how Bixby applies validation conditions in order to reduce the number of ambiguous values.

By default, when a cardinality constraint violation occurs because an input has too many available candidates, Bixby attempts to pre-filter the available candidates using the existing input validations. This runtime flag disables that.

For more information, see Runtime Flags.

Example

capsule {
  ...
  runtime-flags {
    concepts-inherit-super-type-features
    modern-prompt-rejection
    support-halt-effect-in-computed-inputs
    no-filtering-with-validation
  }
}

Deprecation Stages

Learn more about the deprecation stages.

• Stage 1: R19N
• Stage 2: R19O
• End of Life: R19P