Jake Zatecky

Can you elaborate on what you mean by single select?

The library as written does not apply any additional extensions to the node objects. However, this is a straight-forward and reasonable enough use case that it can be a future...

An individual note supports the [`icon`](https://github.com/jakezatecky/react-checkbox-tree#node-properties) property. You can also reference the [`CustomIconsExample`](https://github.com/jakezatecky/react-checkbox-tree/blob/master/examples/src/js/CustomIconsExample.js) file to see how that works in practice.

The primary way is through adding CSS rules. You can look at the [source Sass file](https://github.com/jakezatecky/react-checkbox-tree/blob/master/src/scss/react-checkbox-tree.scss#L14) to get an idea of what styles the component uses.

@RodrigoCarvalho21 Right now you only have really one option. That is to set a CSS rule to hide the icon: ``` css .rct-node-icon { display: none; } ```

@JordyPouw Yes, that is something we could support.

No updates, unfortunately. Accessibility is a high-priority addition, so it will be included in the next release. I admit I have been terrible at finding time in the past. The...

Not yet, unfortunately. I cannot make any promises, but it is still something I intend to add.

As specified in the README, all nodes must have a unique `key` value. This is due to supporting key values in the `checked` and `expanded` properties as well as for...

Nothing seems wrong with those values, but I suspect nodes violating the unique value constraint exist at some point. If you can recreate the issue in a small demo environment,...