Support for autocomplete widget in D8

The attached patch is a band-aid to get rid of the error message. Entity reference has been moved into core and this hook needs to be rewritten to support the autocomplete handler correctly.

As far as I can tell, the code regarding the form widget was still as in D7 and attached is a port of it. Since I am not sure that it is even possible to robustly override hook_widget_form_alter() as happened in D7 I chose to write a separate widget. If someone wants to try to make that work that's fine by me but the attached solution works fine for me at least.

If the RealNameController will be committed to the project I'm willing to provide unit tests for it.

Great, but what about:

Autocomplete matching

• Starts with
• Contains

A configured match operator "Contains" is not working.

This patch confuses me a lot. EntityReferenceAutocompleteWidget.php is completly different and I guess this may not work properly in all cases.

$element += array(
      '#type' => 'entity_autocomplete',
      '#target_type' => $this->getFieldSetting('target_type'),
      '#selection_handler' => $this->getFieldSetting('handler'),
      '#selection_settings' => $this->getFieldSetting('handler_settings'),
      // Entity reference field items are handling validation themselves via
      // the 'ValidReference' constraint.
      '#validate_reference' => FALSE,
      '#maxlength' => 1024,
      '#default_value' => isset($referenced_entities[$delta]) ? $referenced_entities[$delta] : NULL,
      '#size' => $this->getSetting('size'),
      '#placeholder' => $this->getSetting('placeholder'),
    );

you changed the type, maxlength and other stuff.

Hi

Due to another module I couldn't work on this anymore. The comment you are referring to is a left-over, entity_autocomplete isn't used in that variant, I just used it as a starting point.

That being said, there is a bug in the loader for it. You can find and save users but editing the page with that again will cause an error.

To solve this more generally I started extending entity_autocomplete again but haven't gotten very far. I've attached that work-in-progess but that isn't nearly done, I just won't have the time to work on this as much as I'd like this month.

Combined both the patches and rerolled it as the patch was not applying to the latest head.

With this patch I am getting the following error.

Uncaught PHP Exception Symfony\\Component\\Routing\\Exception\\InvalidParameterException: "Parameter "bundle_type" for route "realname.real_name_controller_autocomplete" must match "[^/]++" ("" given) to generate a corresponding URL." at /core/lib/Drupal/Core/Routing/UrlGenerator.php line 199,

Any update on this? Currently I think this is the major issue that is holding back the adoption of this module in Drupal8. If this is fixed the module should be good for an alpha release.

Patch works great for me even patching via composer.

#4, 5, 6, 8 look not like a committable patch.

Patch no longer applies to the latest version and error is back.

Updated and cleaned #9 patch. No errors but still needs work.
When i start fillin into "Authored by" the full name the autocomplete does not work at all. The autocomplete list shows the Full Name but the search does not match by "Full Name".

Number 18 works great for me, thanks!

+++ b/src/Controller/AutocompleteController.php
@@ -0,0 +1,75 @@
+      $matches = $this->getMatched($typed_string);

Why is this not using EntityAutocompleteMatcher? The getMatches() shows how to implement the match param CONTAINS or start with.

+++ b/src/Controller/AutocompleteController.php
@@ -0,0 +1,75 @@
+      $query->condition('r.realname', '%' . $connection->escapeLike($string) . '%', 'LIKE');

This is a CONTAINS only. In D7 we also had "START WITH".

• Has this tested with Entity References?
• I'm wondering how the patch can go down from 25KB to 5KB...

@Ronald: I worked on your patch and implemented the missing START WITH. As it works fine, I just committed it. If you know how to implement this ContentEntity I'm happy to see your patch to move this forward. Let's move this to a follow up case.

Thanks all for the hard work.

I tested both dev and beta1 modules, When user's realname token values are empty, getting empty result in autocomplete widget.

Not sure how this is possible with #2874168: Empty realname bubble into site

Thank you for the quick response @hass.
Getting empty realname in autocomplete widget.
I followed these steps.
1) Installed latest dev module.
2) In realname configuration page, I changed token values. For this token some users have values and some users do not have any value.
3) In node add page, at Author Information section, I searched for the users using auto complete and getting empty result along with realname values.
Strange thing is before performing autocomplete in node add/edit page, realname table has values for users who have token value and after searching for users in autocomplete widget in the table there are empty records for users.

Please post your realname token string in code tags in the referenced case.

Here is token [user:field_first_name] [user:field_last_name].
I created two text fields in the /admin/config/people/accounts/fields with "field_first_name", "field_last_name" machine names.

Can you post this to #2874168: Empty realname bubble into site please!!! It has nothing to do with the issue here.