Set the payment form context in the session

[agibson-godaddy]

Summary

Related: https://github.com/gdcorp-partners/woocommerce-gateway-elavon/pull/103

This sets the page context in the session when rendering the payment forms.

Release: #1234 (release PR)

Details

• Also copied the EnumTrait from mwc-common
• Set up an enum for the contexts

QA

If applicable, add specific steps for the reviewer to perform as part of their QA process prior to approving this pull request. Steps should be in a step -> success? format, like below

Setup

• QA in https://github.com/gdcorp-partners/woocommerce-gateway-elavon/pull/103 passes

Before merge

• I have confirmed these changes in each supported minor WooCommerce version

[nmolham-godaddy]

@agibson-godaddy So, I got carried away a bit here 😅

At first, I wanted to add unit test for the new PaymentFormContextChecker component, so I ended up adding mwc-tests, setup PHPUnit and converting existing codeception unit test to PHPUnit tests along side adding the new class tests

Ref: 34b27ab...dc8f67c

I am not sure why Github doesn't see the 6792-mwcmanaged runner and the job fails straight away instead of the usual hold/pending status until the repo gets added to the pool's repo list. Maybe because this repo is on a different organization level godaddy-wordpress instead of gdcorp-partners ? 🤔

[agibson-godaddy]

@agibson-godaddy So, I got carried away a bit here 😅

At first, I wanted to add unit test for the new PaymentFormContextChecker component, so I ended up adding mwc-tests, setup PHPUnit and converting existing codeception unit test to PHPUnit tests along side adding the new class tests

Ref: 34b27ab...dc8f67c

I am not sure why Github doesn't see the 6792-mwcmanaged runner and the job fails straight away instead of the usual hold/pending status until the repo gets added to the pool's repo list. Maybe because this repo is on a different organization level godaddy-wordpress instead of gdcorp-partners ? 🤔

That could definitely be the problem. Runner pools are per-organization, and every repo added is assumed to be part of that org. So we can't even add this repo to our existing runner pool because of that. We'd have to create a separate runner pool.

I don't know for certain that's what's causing the instant error, but it's definitely a problem anyway that we have to fix!

I can take a look at this today to see if I can get it running. Nice work on the tests!!! 🙌

[agibson-godaddy]

@nmolham-godaddy Reworked to drop mwc-tests dependency and use hosted runners.

[nmolham-godaddy]

LVGTM