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

Set up workflow for edit payments by bank transfer #741

Merged
merged 9 commits into from
Mar 23, 2020

Conversation

irisfaraway
Copy link
Member

https://eaflood.atlassian.net/browse/RUBY-833

This is part of a set of multiple PRs to configure payment when a carrier type changes during editing.

This PR sets up the workflow and pages for paying for an edit by bank transfer. This includes the payment summary and bank transfer info pages.

WorldPay will be added separately in a future PR.

https://eaflood.atlassian.net/browse/RUBY-833

This is part of a set of multiple PRs to configure payment when a carrier type changes during editing.

This PR sets up the workflow and pages for paying for an edit by bank transfer. This includes the payment summary and bank transfer info pages.

WorldPay will be added separately in a future PR.
This includes several new partials which can hopefully be reused on similar pages.
This includes a shared partial which can hopefully be reused on other similar pages.
@irisfaraway irisfaraway added the enhancement New feature or request label Mar 17, 2020
@irisfaraway irisfaraway self-assigned this Mar 17, 2020
@irisfaraway
Copy link
Member Author

This PR looks big, but should be manageable commit-by-commit.

@cintamani
Copy link
Contributor

I am wondering since the layout of the pages is almost the same, why are we generating new forms for these and not reusing the existing ones we already share with new and renewing registrations?

@irisfaraway
Copy link
Member Author

@cintamani We already had different controllers for the copy cards payment pages, so I was following that pattern. There are some differences in the text around options, for example. Although I think that with the way I've rewritten the code, we may now be able to reuse it across all the different payment pages.

I was thinking of getting this merged in as-is and then merging all the various duplicated payment forms in a separate PR so as not to bloat this one even more – what do you think?

Copy link
Contributor

@cintamani cintamani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Go on with it :)

@irisfaraway irisfaraway merged commit 5af705c into master Mar 23, 2020
@irisfaraway irisfaraway deleted the feature/edit-payment-workflow branch March 23, 2020 11:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants