Architectural changes

[kareemmahlees]

No description provided.

[codecov]

Codecov Report

Attention: Patch coverage is 84.76395% with 71 lines in your changes are missing coverage. Please review.

Project coverage is 87.70%. Comparing base (ec4e825) to head (81348a2).

Files	Patch %	Lines
internal/db/pg.go	79.13%	16 Missing and 8 partials ⚠️
internal/db/mysql.go	81.41%	14 Missing and 7 partials ⚠️
internal/db/sqlite.go	84.87%	12 Missing and 6 partials ⚠️
internal/handlers/dbHandlers.go	78.57%	4 Missing and 2 partials ⚠️
internal/server.go	90.47%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master      #10      +/-   ##
==========================================
- Coverage   90.45%   87.70%   -2.76%     
==========================================
  Files          13       14       +1     
  Lines         545      724     +179     
==========================================
+ Hits          493      635     +142     
- Misses         35       60      +25     
- Partials       17       29      +12     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[gitguardian]

⚠️ 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
9462643	Triggered	Generic Password	68f2f90	utils/testHelpers.go	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

• 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.

---

<sup>🦉 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.

Our GitHub checks need improvements? Share your feedbacks!</sup>