Skip to content

Add a more expressive condition language for controls #88

Description

@lan17

Summary

  • Add a more expressive condition language for controls so a single control can combine multiple conditions.

Motivation

  • Some policies need to reason over more than one condition at once, and splitting that logic across several controls is awkward and harder to manage.

Current behavior

  • A control effectively captures a single condition, so more complex logic has to be modeled across multiple controls or pushed into evaluator internals.

Expected behavior

  • A control should be able to express multiple conditions in one place with clear composition semantics.

Reproduction (if bug)

  1. N/A
  2. This is a feature request.
  3. N/A

Proposed solution (optional)

  • Introduce a more expressive control condition model, likely supporting boolean composition such as and, or, and not, while keeping authoring simple.

Activity

  1. added theissue type on Mar 10, 2026
  2. lan17 commented on Apr 4, 2026

    @lan17
    ContributorAuthor

    Closing this as completed.

    This shipped in #115 and merged to main in 2ff4c12 on March 17, 2026.

    That work introduced recursive condition trees so a single control can express nested and / or / not composition, along with rollout compatibility for legacy flat controls, migration support, recursive validation/evaluation, and SDK/UI contract updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions