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

Extract assignPaymentFields #13957

Merged

Conversation

mattwire
Copy link
Contributor

@mattwire mattwire commented Apr 4, 2019

Overview

Proof of concept towards proposed refactor per #13762 (comment)

@eileenmcnaughton I'm thinking this function should be in a new trait that can be shared between CRM_Contribute_Form_ContributionBase and CRM_Event_Form_Registration. Alternatives are we inherit from contributionbase for registration form or make this function static. Thoughts?

@civibot
Copy link

civibot bot commented Apr 4, 2019

(Standard links)

@civibot civibot bot added the master label Apr 4, 2019
@eileenmcnaughton
Copy link
Contributor

@mattwire I was thinking the new FrontEndPaymentFormTrait would be the place. If this is a straight extraction I'm happy to review & merge it even if it later moves again

@mattwire mattwire marked this pull request as ready for review April 4, 2019 20:45
@mattwire
Copy link
Contributor Author

mattwire commented Apr 4, 2019

@eileenmcnaughton Yes, it's a straight extraction. No changes. So we can review, merge and then move to trait + cleanup / make generic enough so it works for event registration

@eileenmcnaughton
Copy link
Contributor

test this please

@eileenmcnaughton
Copy link
Contributor

I redid this locally & got to the same result - merge on pass

@eileenmcnaughton eileenmcnaughton merged commit a076875 into civicrm:master Apr 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants