BUG: References editor shows no results when entering ids

[Sebobo]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

In Neos 8 one could find nodes by pasting the node id into the search box of the references editor.
This was necessary, when the title of a node was not very unique or the search took too long.
This was done before in the NodeSearchService as every term was checked if it is an ID.

In Neos 9 this is not happening anymore, and therefore no result is given for an id.

Expected Behavior

The backend returns a single node, when one enters a valid node id into the search box.

Steps To Reproduce

Copy any content node id and try to reference it in a content references element.

Environment

- Flow: 9.x
- Neos: 9.x
- PHP: any

Anything else?

No response

[bwaidelich]

Just a little note regarding

This was done before in the NodeSearchService as every term was checked if it is an ID

This was actually flawed. It checked whether the string was a UUID, but node ids don't have to be UUIDs (since 2017)

I suppose, we'll have to always search for the id additionally – but maybe it makes sense to only do that if the other search did not yield results?

[bwaidelich]

What about this: neos/neos-ui#4093

[mhsdesign]

Thought about what you sketched as well thank you!

[Sebobo]

I suppose, we'll have to always search for the id additionally – but maybe it makes sense to only do that if the other search did not yield results?

I still feel my past proposal (which I can't find right now and implemented for one customer in Neos 8.3) to have resolvers, something like in the following example, could still be useful:

Vendor:
  Search:
    NodeSearch:
      # Resolvers for various types of inputs which NodeSearchServiceInterface implementations can use to resolve search terms
      resolvers:
        'nodeIdentifier':
          class: 'Vendor\Search\Service\NodeSearchIdentifierResolver'
          position: 'start'
        'nodePath':
          class: 'Vendor\Search\Service\NodeSearchPathResolver'
        'publishedUrl':
          class: 'Vendor\Search\Service\NodeSearchPublishedURLResolver'
        'url':
          class: 'Vendor\Search\Service\NodeSearchURLResolver'

The search in the node tree would need different resolvers than the ones in the reference editor.

[bwaidelich]

@Sebobo I like your proposal (maybe a topic for the next sprint – btw: I will be there \o/)

In the meantime: #5761 should actually fix your issue.

I'd be happy if we could merge neos/neos-ui#4093 too (especially since I have already fixed it a year ago *g)