We think it's an overall improvement, but React is our target package.
Summary
Currently, when users change the "column" attribute in the RuleBuilderEditor, the selected operand and rule value input are not automatically reset or cleared. This can lead to confusion as the previous operand and rule value input remain visible even after the column is changed.
To improve the user experience and avoid confusion, this feature request proposes two enhancements for the RuleBuilder component:
Automatically reset or clear the selected operand and rule value input when the "column" attribute is changed. This will ensure that the component always reflects the current state and selections made by the user.
Optionally, conditionally display the rule value input only after the user has selected an operand option. This will help guide users through the process of building a rule more intuitively, preventing them from inputting a rule value before an appropriate operand has been chosen.
Implementing these enhancements will result in a more user-friendly and intuitive RuleBuilder component, minimizing the risk of incorrect rule configurations and making it easier for users to build complex rules.
Specific timeline issues/requests
We want to use the RuleBuilderEditor component in a project that will start in Q2 2023, so we need a solution for this soon. We would appreciate it if you could help with it.
Available extra resources
You can contact me on IBM Slack for details or any other information.
What package is this for?
We think it's an overall improvement, but React is our target package.
Summary
Currently, when users change the "column" attribute in the
RuleBuilderEditor, the selected operand and rule value input are not automatically reset or cleared. This can lead to confusion as the previous operand and rule value input remain visible even after the column is changed.To improve the user experience and avoid confusion, this feature request proposes two enhancements for the
RuleBuildercomponent:Automatically reset or clear the selected operand and rule value input when the "column" attribute is changed. This will ensure that the component always reflects the current state and selections made by the user.
Optionally, conditionally display the rule value input only after the user has selected an operand option. This will help guide users through the process of building a rule more intuitively, preventing them from inputting a rule value before an appropriate operand has been chosen.
Implementing these enhancements will result in a more user-friendly and intuitive RuleBuilder component, minimizing the risk of incorrect rule configurations and making it easier for users to build complex rules.
Specific timeline issues/requests
We want to use the
RuleBuilderEditorcomponent in a project that will start in Q2 2023, so we need a solution for this soon. We would appreciate it if you could help with it.Available extra resources
You can contact me on IBM Slack for details or any other information.