Submitting Logs for Katch GO

[katchdeveloper]

I have created New pull request to avoid conflict and issue occurred in previous one. Please verify the logs and acknowledge..

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets 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.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-	-	Generic High Entropy Secret	bd0dcfd	logs/KatchGo/flow-1/on_confirm.json	View secret
-	-	Generic High Entropy Secret	2b64b96	logs/KatchGo/flow-1/on_init.json	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 secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
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

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 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.}

[sourabhsaini11]

@katchdeveloper, Kindly continue in that only to maintain a single trail.

[katchdeveloper]

@katchdeveloper, Kindly continue in that only to maintain a single trail.

Actually that request got lots of conflict and errors that's why i have closed that PR here is the new PR but the logs are the same, it's latest updated logs..

[sourabhsaini11]

@katchdeveloper
common_issue

• fulfillments.gps shouldn't be same for each stops
• missing cancel-on_cancel(Soft) pair calls

on_select, on_confirm

• for code ROUTE_ID, value should be of type string

on_init

• missing fulfillment obj having type TICKET
• for code ROUTE_ID, value should be of type string

on_cancel

• incorrect format for order.created_at

[katchdeveloper]

@katchdeveloper common_issue

• fulfillments.gps shouldn't be same for each stops
• missing cancel-on_cancel(Soft) pair calls

on_select, on_confirm

• for code ROUTE_ID, value should be of type string

on_init

• missing fulfillment obj having type TICKET
• for code ROUTE_ID, value should be of type string

on_cancel

• incorrect format for order.created_at

We don't have GPS data of any stop, so to make it structured we assigned the dummy data.
(missing cancel-on_cancel(Soft) pair calls) : Can you please elaborate this, We didn't understand what's that mean..
Other changes are done, can you check and verify.

[sourabhsaini11]

For cancellation, 2 cancel-on_cancel pair calls are required. Kindly refer to api-contract for more info.