Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Ref] [Import] Use processor to determine website type, location type, test #15116

Merged
merged 2 commits into from
Aug 23, 2019

Conversation

eileenmcnaughton
Copy link
Contributor

Overview

Minor cleanup on import

Before

Less readable

After

More readable

Technical Details

Part of a bigger cleanup - I'm slowly extending test cover & making the covered changes.

The way it DID work was an array like
[[0 => 1], [1 => ''],[2 =>'']
was passed around as $mappingWebsiteType. These were basically the values from the column website_type_id from the table civicrm_mapping_field indexed by column number & they were passed around for eventual lookup. We now load the mapping_fields into the ImportProcessor class and use it's functions to look up the values (which are NOT stored in separate column-indexed arrays but in a single array that reflects the underlying data structure from civicrm_mapping_field)

Comments

@civibot civibot bot added the master label Aug 23, 2019
@civibot
Copy link

civibot bot commented Aug 23, 2019

(Standard links)

@eileenmcnaughton
Copy link
Contributor Author

test this please

1 similar comment
@eileenmcnaughton
Copy link
Contributor Author

test this please

@eileenmcnaughton
Copy link
Contributor Author

@seamuslee001 this is passing - just same as similar ones - add a test & make a change to the newly tested line to simplify

@seamuslee001
Copy link
Contributor

Change looks fine and consistent with other work. this has sufficient tests covering this area merging

@seamuslee001 seamuslee001 merged commit 20664a1 into civicrm:master Aug 23, 2019
@seamuslee001 seamuslee001 deleted the import_website branch August 23, 2019 23:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants