We are using the editor in more and more projects and the customers are very happy. Especially on larger sites, it enables the editor to find the correct target document. We are also working on lots of improvements and fixes right now, although its already very solid.
I talked to @Nezaniel and @mficzel and they would be happy to have the feature in the core.
Here are the options and I would like to hear your votes:
Add it as an additional editor to Neos.Ui
Add it as a separate package under the Neos Namespace
Add it as a separate package under the Flowpack Namespace
Things about Code: Hooks and Functional Components vs what we have currently
The Link Editor’s code comes with more modern react functional components and also hooks (via an adaptation layer).
Hooks and FC are not used in the ui currently, we use hoc (the things with the decorators) and class components.
When we keep the adaptation layer of the hooks and move them also in the core we would have two different write forms, but having both options in the ui at the same time could help to migrate eventually all code to functional components with hooks and gives 3rd party authors (you and me ) fancier tools.
Yes the editor would be renamed. Question is wether it should replace the current LinkEditor, in that case it should support starting points outside the current site or wether it schould be an alternative with a distinct name. How about LinkDialogEditor