Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]: Insufficient support for custom operators in ConditionBuilder #6422

Open
2 tasks done
pjborowiecki opened this issue Nov 13, 2024 · 0 comments
Open
2 tasks done

Comments

@pjborowiecki
Copy link

Package

Carbon for IBM Products

Description

Although addition of custom components is currently supported, it is not sufficiently flexible. Trying to add add a custom operator to all kinds of fields (e.g. number, text, select, date) requires creating a custom component for all of those types.

Having the ability to modify or extend built-in operators is critically important and needs to be supported.

For example, there is currently no straightforward way of using something like "has value" / "has no value" in the ConditionBuilder, without firt replacing all built-in field types with custom ones.

Component(s) impacted

ConditionBuilder

Browser

Chrome, Safari, Firefox, Microsoft Edge

@carbon/ibm-products (previously @carbon/ibm-cloud-cognitive) version

2.50.0

Suggested Severity

Severity 2 = Aspects of design is broken, and impedes users in a significant way, but there is a way to complete their tasks. Affects major functionality, has a workaround.

Product/offering

IBM

CodeSandbox or Stackblitz example

https://codesandbox.io

Steps to reproduce the issue (if applicable)

No response

Release date (if applicable)

No response

Code of Conduct

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Needs triage 🧐
Development

No branches or pull requests

1 participant