The component uses copy&pasted code of React Select v1. This hinders updates, as React Select has been completely rewritten and is now at version 5.
The goal is to remove the copy&pasted code and replace it with the React Select component usage.

Accidentally, while selecting terms in the tree, I get the following error.

index.js:2177 Warning: Can't call setState (or forceUpdate) on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in the componentWillUnmount method.
in TooltipItem (at resultItem.js:104)
in div (at resultItem.js:91)
in ResultItem (created by Connect(ResultItem))
in Connect(ResultItem) (at App.js:296)

Extend the component API to support Objects in subterms (not just IRI list).

As a developer, I want to use the tree select in applications using React 18. Currently, the library's peer dependency on React is restricted to 17.x.x.

The "Create new option" form doesn't work at all.

Here are couple of problems I have encountered.

1. Selecting a term from the dropdown doesn't actually select the term
2. Items don't fit in the dropdown causing overlapping individual items
3. The tree structure is not present, all items are in one level without the possibility of expanding nor collapsing

Here is an image showing one of the issues:

As a user, I don't want the component to have reactstrap as a dependency in case I am using another bootstrap-based library (like react-bootstrap).

Therefore, all reactstrap component references should be extracted and either replaced with pure bootstrap or configurable alternatives.

As a developer, I need the tree component to be able to display options with multiple parents. That is, an option would be displayed in more than one (sub)trees.

How do I use the IntelligentTreeSelectComponent in an NPM-based project?

The component does not get updated the list of options. When rerendered and the list size does not change, the list of options remains the same.

This manifestated in TermIt, when editing a term and showing the available types to pick from - switching between "cs" and "en" does not update the list.

When multi is set to false, custom value renderer is not taken into account and the default react-select one is used. The property should work for both single and multiselect.

Upon running the project according to the instructions in README.md, clicking on Filter and deselecting 'Multiselect', the following error occurs:

Accidentally, when creating a new term, clicking the submit button fails (nothing happens, no action is triggered). One of the failing scenario was - fill all term details except of term children and click submit.

When the 'name' attribute is assigned, the options are cached, this is correct.
When the 'name' attribute is not assigned, the options are still cached, but into an empty storage. This is not correct

When the tree is rendered with open menu and the input does not have focus, clicking on an option does not select it. Instead, the input gets focus. Only the second click selects the option.

Hi Team,

We are using intelligent-tree-select in the reactjs app. From the below screenshot, if we type 'comp amount' in the search box and hit enter, it should be selected. But its not working. Instead, the value inside onChange handler has only the first value in the from the options. Please suggest a fix

As a part of major rewrite and simplification of the component, several features have been removed. Tooltip is one of them, as its content was difficult to read and it was often displayed in incorrect places.

However, a tooltip showing details of an option is a useful feature.

• Its implementation should be independent of reactstrap or other React implementations of Bootstrap.
• The contents of the tooltip should be configurable.

Currently, the labelKey property has to be a string representing the name of the label attribute. For various reasons (e.g., support for localized labels), it would be useful to be able to specify a function to be used for label retrieval.

During component loading (page refresh), the following error is logged into the console.

"Warning: Failed prop type: The prop addonType is marked as required in InputGroupButton, but its value is undefined."

npm start produces Parse error:

.../src/main/webapp/node_modules/intelligent-tree-select/lib/App.css:1
.result-item{
^
ParseError: Unexpected token

In the previous version (before conversion from react-select v1 to v5), the expanded prop forced the tree to be fully expanded. This behaviour is no longer available