Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Alerting] Remove use of any from public APIs in Triggers UI #66257

Closed
gmmorris opened this issue May 12, 2020 · 3 comments
Closed

[Alerting] Remove use of any from public APIs in Triggers UI #66257

gmmorris opened this issue May 12, 2020 · 3 comments
Labels
Feature:Alerting/RulesManagement Issues related to the Rules Management UX Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) technical debt Improvement of the software architecture and operational architecture

Comments

@gmmorris
Copy link
Contributor

We have an issue to remove all any from Triggers UI here: #66256

That issue is large and we do not feel (as discussed in the weekly sync on 11th May 2020) that it's needed for GA.
But we do feel that we should remove all any from the public APIs (Components consumed by other plugins and Types for passing components into AlertTypes & ActionTypes) before GA, so this issue is to address those public APIs.
@gmmorris gmmorris added Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels May 12, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

@gmmorris gmmorris changed the title [Alerting} Remove use of any from public APIs in Triggers UI [Alerting] Remove use of any from public APIs in Triggers UI May 12, 2020
@mikecote mikecote mentioned this issue May 12, 2020
Closed
@YulNaumenko
Copy link
Contributor

@gmmorris this issue feels like the same as #66256.
Do you think we can close one of this?

@YulNaumenko YulNaumenko added the technical debt Improvement of the software architecture and operational architecture label Mar 11, 2021
@gmmorris gmmorris added the Feature:Alerting/RulesManagement Issues related to the Rules Management UX label Jul 1, 2021
@gmmorris
Copy link
Contributor Author

gmmorris commented Jul 1, 2021

The idea was to do this one sooner than #66256 but that didn't happen, so closing this one as the other covers this as well

@gmmorris gmmorris closed this as completed Jul 1, 2021
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature:Alerting/RulesManagement Issues related to the Rules Management UX Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) technical debt Improvement of the software architecture and operational architecture
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@gmmorris @kobelb @elasticmachine @YulNaumenko