fix: Remove Visa Checkout#1653
Conversation
Dependency Review✅ No vulnerabilities found.Scanned Files
|
saralvasquez
left a comment
There was a problem hiding this comment.
If we are removing the visa checkout module all together is it worth deprecating values that can't be used instead of removing them?
I sort of took 2 approaches: delete where we could delete and deprecate where we needed to. So, for example the VisaCheckout module was fully deleted since it is never actually released and published. For the Configuration properties those were left and given a |
Ah I didn't notice that commented out publishing for VisaCheckout. This approach makes sense to me! |
Summary of changes
AI Usage
Which AI Agent Was Used?
How was AI used?
Used Claude to find and remove the majority of the Visa Checkout code. I also used Claude to verify there were tests still in place for if a configuration response has Visa Checkout enabled that we will simply ignore. Finally, Claude was used to find a bug where the project would not build after everything seemed to be safely deleted. It turns out one of the payment buttons was actually pointing to a Visa Checkout "Blue" color reference instead of the correct one (They were the same color, so no change)
Estimated AI Code Contribution
Checklist
Authors