-
Notifications
You must be signed in to change notification settings - Fork 43
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
Upgrade to Adyen.Web Dropin/Components V6 #352
base: main
Are you sure you want to change the base?
Conversation
Moved v5 to its own /_archive/v5 folder
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work. I have made some in-line comments
- name: Start checkout-example-advanced container | ||
run: docker run --rm -d --name checkout-example-advanced-v5 -p 8080:8080 -e ADYEN_API_KEY="${{ secrets.ADYEN_API_KEY }}" -e ADYEN_MERCHANT_ACCOUNT=${{ secrets.ADYEN_MERCHANT_ACCOUNT }} -e ADYEN_CLIENT_KEY=${{ secrets.ADYEN_CLIENT_KEY }} -e ADYEN_HMAC_KEY=${{ secrets.ADYEN_HMAC_KEY }} checkout-example-advanced-v5:latest | ||
- name: Run testing suite | ||
run: docker run --rm --name adyen-testing-suite -e PLAYWRIGHT_FOLDERNAME=advanced-checkout/v5 -e ADYEN_HMAC_KEY=${{ secrets.ADYEN_HMAC_KEY }} --network host ghcr.io/adyen-examples/adyen-testing-suite:main |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Setting PLAYWRIGHT_FOLDERNAME=advanced-checkout/v5
is correct, but the E2E testing for Advanced Flow needs to be updated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one has been updated, I've added the v6 e2e tests in the same e2e-checkout-advanced.yml
-file
@@ -1,105 +1,143 @@ | |||
const clientKey = document.getElementById("clientKey").innerHTML; | |||
const type = document.getElementById("type").innerHTML; | |||
const { AdyenCheckout, Dropin } = window.AdyenWeb; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We used to have a single file adyenImplementation.js
for drop-in and components, but now we probably want to create individual files (dropin.js
, ideal.js
, card.js
, etc..) I think.
Similarly to the Vue implementation we can keep those separated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will do that
checkout-example-advanced/src/main/resources/static/adyenImplementation.js
Outdated
Show resolved
Hide resolved
checkout-example-advanced/src/main/resources/static/adyenImplementation.js
Outdated
Show resolved
Hide resolved
Change holder name to "J. Smith"
Description
This PR addresses the upgrade to Adyen.Web Dropin v6.x.x (frontend), see: https://github.com/Adyen/adyen-web/releases/tag/v6.6.0
Additional steps
Notes:
It currently only addresses "Drop-in", will add the Components initial review: