feat: added testing using vitest and ink-testing#1
Open
Aniket-508 wants to merge 6 commits intomainfrom
Open
Conversation
- Add vitest, @vitest/coverage-v8, ink-testing devDependencies - Add test, test:watch, and test:coverage scripts - Configure Vitest with Node env and registry __tests__ glob Made-with: Cursor
- Re-export ink-testing helpers and KEY from a single entry point - Wrap renderTui with registry ThemeProvider for useTheme() in tests Made-with: Cursor
- Cover bar/line/pie charts, heat map, gauge, sparkline, token usage - Cover spinner, skeleton, clocks, timers, stopwatch, toasts, streaming text Made-with: Cursor
- Cover text, password, email, number, masked, path, search, tag inputs - Cover select, multi-select, checkbox group, radio, toggle, pickers - Cover confirm, form, form-field, command palette, and menu Made-with: Cursor
- Cover box, stack, grid, columns, center, scroll view, aspect ratio - Cover table, list, JSON, log, markdown, diff, trees, file picker - Cover virtual list, data grid, pagination, git status, file change Made-with: Cursor
- Cover modal, dialog, drawer, popover, banner, tabs, sidebar, breadcrumb - Cover app shell, login/setup/welcome flows, wizard, help and splash screens - Cover AI-style blocks, usage monitor, notifications, theme and error boundary Made-with: Cursor
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 29737646 | Triggered | Generic Password | 79d0ef2 | registry/ui/tests/password-input.test.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 secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- 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.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.