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

close #238 follow order state machine for payway_v2 #239

Merged
merged 3 commits into from
Mar 4, 2025

Conversation

theachoem
Copy link
Collaborator

@theachoem theachoem commented Jan 3, 2025

Processing Flow

After paid, ABA push back to BookMe+, then it will process payment & order in queue with following steps:

image

BookMe+ Payment V2 Sequence Diagram 5-min

Demo

Screen.Recording.2025-02-05.at.11.20.53.in.the.morning.mp4

@theachoem theachoem changed the base branch from develop to 236-fix-rubocop-linter January 3, 2025 02:43
@theachoem theachoem force-pushed the 238-follow-order-state-machine branch from 0f08882 to 43f4b82 Compare January 3, 2025 03:27
@theachoem theachoem self-assigned this Jan 3, 2025
@theachoem theachoem added the enhancement New feature or request label Jan 3, 2025
@theachoem theachoem force-pushed the 236-fix-rubocop-linter branch from 4bd9170 to 3e6f86c Compare January 10, 2025 05:30
@theachoem theachoem force-pushed the 238-follow-order-state-machine branch from 43f4b82 to 2b3f867 Compare January 10, 2025 05:31
@theachoem theachoem force-pushed the 236-fix-rubocop-linter branch from 3e6f86c to 597f4a0 Compare January 16, 2025 02:58
@theachoem theachoem force-pushed the 238-follow-order-state-machine branch 8 times, most recently from 3e347cd to 30df585 Compare January 21, 2025 02:59
@theachoem theachoem changed the title close #238 follow order state machine close #238 follow order state machine for payway_v2 Jan 21, 2025
@theachoem theachoem force-pushed the 238-follow-order-state-machine branch 5 times, most recently from be24ac1 to 575bd4a Compare January 23, 2025 05:31
@theachoem theachoem force-pushed the 236-fix-rubocop-linter branch from 597f4a0 to 3c49421 Compare January 23, 2025 05:37
@theachoem theachoem force-pushed the 238-follow-order-state-machine branch 3 times, most recently from 0e6eb98 to 1ef147f Compare January 28, 2025 16:56
@theachoem theachoem force-pushed the 238-follow-order-state-machine branch 5 times, most recently from 24f1005 to 5a3c639 Compare January 31, 2025 03:36
@theachoem theachoem force-pushed the 238-follow-order-state-machine branch 13 times, most recently from c05bb44 to 10e8efb Compare February 28, 2025 10:48
@theachoem theachoem changed the base branch from 236-fix-rubocop-linter to develop February 28, 2025 10:55
Copy link

gitguardian bot commented Feb 28, 2025

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
15789919 Triggered Generic High Entropy Secret 4501d6f spec/services/vpago/payment_url_constructor_spec.rb View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@theachoem theachoem force-pushed the 238-follow-order-state-machine branch from 10e8efb to e3dac49 Compare February 28, 2025 10:55
@theachoem theachoem requested a review from channainfo February 28, 2025 11:50
@theachoem theachoem force-pushed the 238-follow-order-state-machine branch 2 times, most recently from 373e736 to fd475fb Compare March 3, 2025 08:44
@theachoem theachoem changed the base branch from develop to 236-fix-rubocop-linter March 3, 2025 09:46
@theachoem theachoem force-pushed the 238-follow-order-state-machine branch 2 times, most recently from bcc2d98 to a265735 Compare March 3, 2025 10:07
@channainfo channainfo changed the base branch from 236-fix-rubocop-linter to develop March 4, 2025 09:30
With 4 api routes for all payment methods. This will help integrating spree_vpago much easier.
- GET: /vpago_payments/checkout (HTML)
- GET: /vpago_payments/processing (HTML)
- GET: /vpago_payments/success (HTML)
- POST: /vpago_payments/process_payment (JSON) - (This is API to process the payment, can call from ABA or our app)
@theachoem theachoem force-pushed the 238-follow-order-state-machine branch from a265735 to 4501d6f Compare March 4, 2025 09:31
@channainfo channainfo merged commit 9ae1b5f into develop Mar 4, 2025
2 checks passed
@theachoem theachoem deleted the 238-follow-order-state-machine branch March 4, 2025 10:25
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.

Follow order state machine
2 participants