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
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | address_autocomplete-webform-integration-3310478-2.patch | 965 bytes | chrisolof |
Issue fork address_autocomplete-3310478
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
chrisolofThe attached patch adds the basic webform integration via a new "Advanced address with autocomplete" webform element.
Comment #3
chrisolofComment #5
geoffreyr commented@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.autocompleteas a library dependency, soui_autocompleteisn'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.
Comment #7
geoffreyr commentedI'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?
Comment #13
vaish commented@geoffreyr I decided to merge patch from #2 because I've been using it for a along time in production while I'm not familiar with the seemingly unrelated changes you added to MR !6. Could you please open up new issue for your changes where you would explain which problem you are trying to solve.
Comment #14
geoffreyr commented@vaish Thanks, will do.