-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add comments to some alerting plugin public API items #101551
Add comments to some alerting plugin public API items #101551
Conversation
…acey-gammon/kibana into 2021-06-07-alert-comments-api-cleanup
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
@elasticmachine merge upstream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with some minor wording nits!
Co-authored-by: ymao1 <[email protected]>
Co-authored-by: ymao1 <[email protected]>
Co-authored-by: ymao1 <[email protected]>
💚 Build SucceededMetrics [docs]Public APIs missing comments
Public APIs missing exports
Page load bundle
History
To update your PR or re-run it, just comment with: |
* master: (68 commits) skip flaky suite (elastic#94043) skip flaky suite (elastic#102012) [esArchive] Persists updates for management/saved_objects/* (elastic#101992) skip flaky suite (elastic#101449) remove unnecessary hack (elastic#101909) [Exploratory View] Use human readable formats (elastic#101520) [Expressions] Refactor expression functions to use observables underneath (elastic#100409) [esArchives] Persist migrated Kibana archives (elastic#101950) [kbnArchiver] fix save to non-existent file (elastic#101974) [Enterprise Search] Add owner and description properties to kibana.json (elastic#101957) [DOCS] Fixes terminology in Stack Monitoring:Kibana alerts (elastic#101696) [Observability] [Cases] Cases in the observability app (elastic#101487) [Alerting][Docs] Combine rule creation and management pages (elastic#101498) temporarily disable build-buddy [Fleet] Fix fleet server collector in case settings are not set (elastic#101752) [Event Log] Populated rule.* ECS fields for alert events. (elastic#101132) [APM] Fleet support for merging input.config values with other nested properties in the policy input (elastic#101690) Add comments to some alerting plugin public API items (elastic#101551) [Alerting][Docs] Moving alerting setup to its own page (elastic#101323) remove uptime public API, it's not used. (elastic#101799) ...
Friendly reminder: Looks like this PR hasn’t been backported yet. |
* Add comments. Remove ruleType as the second param, not needed. * Add comments. Remove ruleType as the second param, not needed. * Fix bad type check and update docs * update docs * Remove unused import * change exports to type to avoid increasing bundle size * Update x-pack/plugins/alerting/public/plugin.ts Co-authored-by: ymao1 <[email protected]> * Update x-pack/plugins/alerting/public/plugin.ts Co-authored-by: ymao1 <[email protected]> * Update x-pack/plugins/alerting/public/plugin.ts Co-authored-by: ymao1 <[email protected]> Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: ymao1 <[email protected]>
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
) * Add comments. Remove ruleType as the second param, not needed. * Add comments. Remove ruleType as the second param, not needed. * Fix bad type check and update docs * update docs * Remove unused import * change exports to type to avoid increasing bundle size * Update x-pack/plugins/alerting/public/plugin.ts Co-authored-by: ymao1 <[email protected]> * Update x-pack/plugins/alerting/public/plugin.ts Co-authored-by: ymao1 <[email protected]> * Update x-pack/plugins/alerting/public/plugin.ts Co-authored-by: ymao1 <[email protected]> Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: ymao1 <[email protected]> Co-authored-by: Stacey Gammon <[email protected]> Co-authored-by: ymao1 <[email protected]>
AlertNavigationHandler
. No consumers were using it and it seems like it should be extractible from the rule that is passed in. Having it as a second parameter opens the door for passing in a rule type that the first parameter's rule doesn't match. What should happen then?Before:
After: