Proposal: New checkbox component to replace iCheck dependency

[ChaoLiangSuper]

The iCheck lib is out of date and not been updated for months. So, we might need our own checkbox component.

Types of issue

• Replace existed component
• Deprecate react-icheck Deprecate iCheck dependency #727

Description

• Build a new checkbox component
• Remove the old dependency

[lightbringer1991]

if it is not so much different than iCheck, we can fork the library and maintain it ourselves (e.g. fixing bugs or implement new logic), without having to reinvent the wheel.

[ChaoLiangSuper]

@lightbringer1991 Sorry for the late update, I didn't get the notification for your comment 😂. I think to redo the icheck component because we can also reduce the size of our project. For instance, those themes in icheck we don't need them.

[omgaz]

Some things to consider

• Should try to support a painless migration from iCheck.
• Should support radio and checkbox (returning a single value).
• Should support checkbox groups (returning an array or key/values).
• Should support radio groups (validating only one is selected).
• Should support labels.
• Should support disabled state.
• Should accept custom classes
• Should accept data-test-selector attribute
• Should accept onChange methdod
• Should not support themes or style customisations.

Follow-up PR:

• Should support NEW functionality of a tri-state.

[ChaoLiangSuper]

PR got merged. Closing this issue.

[omgaz]

This issue is not yet resolved, the radios have not yet been implemented as part of this issue - it's only halfway there.

[lightbringer1991]

if @nimishjha is busy with something else, I can give it a try on Radio buttons.

[lightbringer1991]

reopen since icheck has not been removed yet.

[ChaoLiangSuper]

Closing this issue and open another issue for removing the iCheck lib.
#727