Closed (fixed)
Project:
Salesforce Suite
Version:
8.x-4.x-dev
Component:
salesforce_webform.module
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
12 Apr 2019 at 18:14 UTC
Updated:
9 Jan 2020 at 19:39 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
acrosmanI'm happy to work on getting this started, but I'm looking for feedback on whether this should be handled as a separate plugin entirely or if it should be included as part of the existing plugin and just detect the trait and search of a map. Left to my own devices I'm inclined toward to separate plugin.
Comment #3
acrosmanFixed totally incorrect title.
Comment #4
acrosmanInitial patch attached. Provides a second webform field mapping plugin to handle webform module's entity plugins. Right now it detects them via naming convention, which seems less than ideal but works on the webform core element just fine.
Comment #5
acrosmanComment #6
aaronbaumanLooks like this should implement getDependencies and isAllowed to add conditionality on webform_entity module
See \Drupal\salesforce_mapping\Plugin\SalesforceMappingField\PropertiesExtended for example
Comment #7
acrosmanUpdated patch to include dependency checking. Also fixes an issue with entity autocomplete fields getting skipped for mappings.
Comment #8
acrosmanComment #9
aaronbaumanHere's an updated version with changes from #3065470: getConfigurationOptions should return all the element for the webform
Also, now that I'm looking more closely, why are we doing this in ::value()?
I'm guessing this is cruft from 7.x, but let me know if you know a reason we should keep it.
Comment #10
aaronbaumanand the patch
Comment #11
aaronbaumanComment #13
aaronbaumanThis is in