# Node MENU suggestion

**URL:** <https://discourse.nodered.org/t/node-menu-suggestion/81219>\
**Category:** Core Development\
**Created:** [12 September 2023 05:29 UTC](https://discourse.nodered.org/t/node-menu-suggestion/81219 "2023-09-12T05:29:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [12 September 2023 05:29 UTC](https://discourse.nodered.org/t/node-menu-suggestion/81219/1 "2023-09-12T05:29:05Z")

</div>

Nodes like the `string` are a good example.

You are given a drop down list and sod's law says it will always be at/near the bottom.

A _SEARCH_ option would be nice.  
So I can _search_ for `replace` and get `replaceALL` shown quickly.  
Ok, maybe not calling is search. Type-ahead prediction?

There are other nodes which have this problem but just now I can't remember them.

The `link` nearly has this problem but it does have a search option. So that negates it from this list.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [11 November 2023 05:29 UTC](https://discourse.nodered.org/t/node-menu-suggestion/81219/2 "2023-11-11T05:29:34Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.