Uploaded image for project: 'HAL'
  1. HAL
  2. HAL-1573

Enhance evaluation of boolean expressions

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Unresolved
    • Major
    • None
    • None
    • None
    • None

    Description

      Many resources contain flags in form of boolean attributes. Common examples are

      "enabled" => {
          "type" => BOOLEAN,
          "expressions-allowed" => true,
      }
      

      or

      "statistics-enabled" => {
          "type" => BOOLEAN,
          "expressions-allowed" => true,
      }
      

      If the value of these attributes is an expressions, the attribute cannot be easily evaluated as either true of false. This is an issue when the UI state depends on a concrete boolean value.

      For example, the available actions in the datasource column depend on the enabled state of the datasource. If enabled is an expression it is unknown when the datasource is read from the management model. In this case the enabled state is set to false which might not reflect the real state (in case the expression evaluates to true).

      Find a way to have a defined UI state even if the boolean attributes contain expressions.

      Attachments

        Issue Links

          Activity

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: HAL

              People

                Unassigned Unassigned
                hpehl@redhat.com Harald Pehl
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated: