qwik
qwik copied to clipboard
tRPC & Prisma command/starter
What is it?
- [X] Feature / enhancement
- [ ] Bug
- [ ] Docs / tests
Description
I added the tRPC + Prisma starter Close #1948
Checklist:
- [X] My code follows the developer guidelines of this project
- [X] I have performed a self-review of my own code
- [X] I have made corresponding changes to the documentation
- [ ] Added new tests to cover the fix / functionality
Run & review this pull request in StackBlitz Codeflow.
Looking good @gioboa. You'll need to run yarn fmt
locally and push the result to get CI to pass. :+1:
@gioboa can you please resolve the conflicts? (and let's merge this sucker :)
Thanks!
⚠️ 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.
🔎 Detected hardcoded secrets in your pull request
GitGuardian id | Secret | Commit | Filename | |
---|---|---|---|---|
- | Google API Key | afd0b23c35f11a56b742d748b5737bf5d7e21fae | packages/docs/scripts/showcase.js | View secret |
- | Google API Key | 1ba80734caf14d2e7e3e95e531cc831fc807b0e9 | packages/docs/scripts/showcase.js | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- 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.
Our GitHub checks need improvements? Share your feedbacks!
@manucorporat Waiting to be able to try this out, looks great ...
I close this PR because is based on old code (Nov 2022) and I will create a new one with more details.