kibana
https://github.com/elastic/kibana
TypeScript
Your window into the Elastic Stack
Triage Issues!
When you volunteer to triage issues, you'll receive an email each day with a link to an open issue that needs help in this project. You'll also receive instructions on how to triage issues.
Triage Docs!
Receive a documented method or class from your favorite GitHub repos in your inbox every day. If you're really pro, receive undocumented methods or classes and supercharge your commit history.
TypeScript not yet supported431 Subscribers
Add a CodeTriage badge to kibana
Help out
- Issues
- Failing test: Jest Tests.x-pack/plugins/security_solution/public/attack_discovery/pages - AttackDiscovery when connectors are configured and didInitialFetch is false does NOT render the loading callout
- Failing test: Jest Tests.x-pack/plugins/security_solution/public/attack_discovery/pages - AttackDiscovery when connectors are configured and didInitialFetch is false does NOT render the empty prompt
- Failing test: Jest Tests.x-pack/plugins/security_solution/public/attack_discovery/pages - AttackDiscovery when connectors are configured and didInitialFetch is false does NOT render attack discoveries
- Failing test: Jest Tests.x-pack/plugins/security_solution/public/attack_discovery/pages - AttackDiscovery when connectors are configured and didInitialFetch is false does NOT render the upgrade call to action
- Failing test: Jest Tests.x-pack/plugins/security_solution/public/attack_discovery/pages - AttackDiscovery when connectors are configured, connectorId is undefined, and didInitialFetch is false does NOT render the animated logo, because connectorId is undefined
- Failing test: Jest Tests.x-pack/plugins/security_solution/public/attack_discovery/pages - AttackDiscovery when connectors are configured, connectorId is undefined, and didInitialFetch is false does NOT render the summary
- Failing test: Jest Tests.x-pack/plugins/security_solution/public/attack_discovery/pages - AttackDiscovery when connectors are configured, connectorId is undefined, and didInitialFetch is false does NOT render the loading callout
- Failing test: Jest Tests.x-pack/plugins/security_solution/public/attack_discovery/pages - AttackDiscovery when connectors are configured, connectorId is undefined, and didInitialFetch is false renders the empty prompt
- Failing test: Jest Tests.x-pack/plugins/security_solution/public/attack_discovery/pages - AttackDiscovery when connectors are configured, connectorId is undefined, and didInitialFetch is false does NOT render attack discoveries
- Failing test: Jest Tests.x-pack/plugins/security_solution/public/attack_discovery/pages - AttackDiscovery when connectors are configured, connectorId is undefined, and didInitialFetch is false does NOT render the upgrade call to action
- Docs
- TypeScript not yet supported