feat: Docs search #1058
feat: Docs search #1058
Conversation
|
| GitGuardian id | Secret | Commit | Filename | |
|---|---|---|---|---|
| - | Algolia Keys | 460923b | packages/docs/.env | View secret |
| 4241586 | Generic High Entropy Secret | f79f715 | packages/docs/src/components/header/header.tsx | View secret |
| 4241586 | Generic High Entropy Secret | 3f2a8bd | packages/docs/src/components/header/header.tsx | View secret |
| 4241586 | Generic High Entropy Secret | ba3f77a | packages/docs/src/components/header/header.tsx | View secret |
| 4241586 | Generic High Entropy Secret | f593238 | packages/docs/src/components/header/header.tsx | 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!
|
preview on https://yb-qwik.pages.dev/ |
|
Amazing job! However I am a bit concerned about the eagerness of executing all react to support this. I would look into QwikReact to not run jS until the user interacts with the searchbar |
and could I help with write whole widget in qwik at all ? maybe functionality & accessible feature not comparable to official one, but I will try my best. |
|
progress update: finished the MVP of search written in Qwik. Preview available in the same link https://yb-qwik.pages.dev/ . while it still can be improved for sophisticated UI, But I think it can be done later. There is some issues currently I'm blocked for importing qwik components in npm when I import bundled component, showing following errors Tried:
|
|
can i see the repo of qwik-algolia search? |
|
Found it! going to see if i can debug the issues with |
* main: feat: allow typeof onGet for DocumentHead (QwikDev#1065) docs: fix Syntax Error in React Counter Component (QwikDev#1076) docs: Add missing endpoint types to routing overview. (QwikDev#1064) fix: cloudflare pages starter (QwikDev#1083) feat: static site generation (QwikDev#1048) fix: root styles rendering (QwikDev#1095) docs: clarify useEffect usage a bit that can watch (QwikDev#1090) fix: useMount rendering order is respected (QwikDev#1094) feat: add Yaml Type (QwikDev#1086) fix: useClientEffect() runs in client-side mounted cmps (QwikDev#1092) feat: containerAttributes (QwikDev#1089) fix: properly serialize resources (QwikDev#1087) feat/fix: Export mdx frontmatter variables to the developer (QwikDev#1075) docs: Update README.md - Fix broken links (QwikDev#1071)
Co-authored-by: Félix Sanz <me@felixsanz.com>
* fix(css): correctly process vendor prefix and animation * fixup! fix(css): correctly process vendor prefix and animation
|
Thank you soo much! This was an amazing amount of work! Brilliant! |
8 participants
What is it?
Description
see docs/readme.md
Use cases and why
Checklist: