Webform integration

Created on 19 September 2022, almost 2 years ago
Updated 29 March 2023, about 1 year ago

Problem/Motivation

Ideally this autocomplete functionality would work in webforms as well.

Steps to reproduce

Proposed resolution

Expose an address_autocomplete webform element.

Remaining tasks

User interface changes

API changes

Data model changes

✨ Feature request
Status

Needs review

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States chrisolof

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • First commit to issue fork.
  • πŸ‡¦πŸ‡ΊAustralia geoffreyr

    @chrisolof Looks good so far. I've created an issue fork and added your patch to it, plus a tiny change to add core/drupal.autocomplete as a library dependency, so ui_autocomplete isn't seen as null or undefined.

    What I'd like to do next is write a crosswalk between xAL property names and each of the fields that we're autocompleting into. I'll keep the existing property mappings so current implementations don't change.

    I've got a few more feature ideas, but they might be better off kept to other requests.

  • @geoffreyr opened merge request.
  • πŸ‡¦πŸ‡ΊAustralia geoffreyr

    I've done a pass at the merge request. One thing that occurs to me is that we might want the crosswalk to be configurable, depending on the autocomplete service that's being used. Do you think we should make that a setting instead, with some sensible defaults?

Production build 0.69.0 2024