-
### Describe the bug
when using p-treeselect component in checkbox selection mode with filter and filtering child nodes, selecting all filtered nodes - as a result higher nodes selecting as fully sel…
-
### Describe the bug
In our use case, we have a index builder, builds the index using `usearch.save()`.
And there are multiple queryer, accessing the index using `usearch.view()`.
I found that …
-
![Screenshot 2024-07-23 113441](https://github.com/user-attachments/assets/0d570aa9-ab6e-4819-ba2b-ae27d92e8f85)
After changing gravity and other parameters i cant seem to prevent the overlap of the …
Ad-4m updated
1 month ago
-
**Describe the bug**
Tree is used in controlled mode for selectedIds.
User selects some Ids.
Then user searches for some text (filtering scenario) and some of selected items are disappeared from t…
-
### Specification
With network segregation we will potentially have separate networks to keep track of. So when finding a node within a specific network, it will actively work against us to search …
-
Filtering of the nodes is working as supposed to be.
But we re unable to select/unselect a node after filtering.
-
Do we want to add a deceased checkbox to Person node. This will be helpful for early career folks who may try to reach out to someone they don't realize is deceased. More importantly, it will also all…
-
Since Lightbeam allows users to enable Tracking Protection from inside the web extension, it would be really cool to show them what kind of difference this makes by applying a tracking protection filt…
-
### Describe the bug
Resulting node(s) cannot be be clicked after filtering in Tree component with Multiple Selection with Checkbox. Also console errorr as "ERROR RangeError: Maximum call stack siz…
-
With the data saved as a network, it could be interesting to use network analytic tools to produce descriptive statistics of the network. This may include:
+ Summary higher degree nodes (musicians/…