Comfy-Org / Comfy-Org/ComfyUI_frontend
Incorrect priority of API nodes in search
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 704
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 512
Description
### Prerequisites
- [x] I am running the latest version of ComfyUI
- [ ] I have custom nodes enabled
### What happened?
When using new Nodes Search, API nodes always show first.
Since the [previous issue](https://github.com/Comfy-Org/ComfyUI_frontend/issues/10333) was falsely marked as completed, I'm opening the new one. Deprioritization is still unfixed, and the [explanation](https://github.com/Comfy-Org/ComfyUI_frontend/issues/10333#issuecomment-4103269465) that was given only proves that it its a bug (even if it's intentional):
There's literally no "get" in any on the nodes names.
ComfyUI 0.18.1, ComfyUI_frontend v1.43.2
### Steps to Reproduce
1. Use ComfyUI with the new Nodes Search
2. Search for "Get"
### How is this affecting you?
Feature doesn't work as expected
### ComfyUI Frontend Version
1.43.2
### Browser
Chrome/Chromium
### Console Errors
```javascript
```
### Logs
```shell
```
### Additional Context
_No response_
┆Issue is synchronized with this [Notion page](https://www.notion.so/Issue-10394-Incorrect-priority-of-API-nodes-in-search-32b6d73d365081c88328ec4dd8f6c27a) by [Unito](https://www.unito.io)
Contributor guide
Assessment
This issue has not been assessed yet.