-
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
Creating alert link with alert id and rule id #140634
Creating alert link with alert id and rule id #140634
Conversation
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!
💚 Build Succeeded
Metrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: |
@@ -14,8 +14,10 @@ export const paths = { | |||
rules: RULES_PAGE_LINK, | |||
ruleDetails: (ruleId?: string | null) => | |||
ruleId ? `${RULES_PAGE_LINK}/${encodeURI(ruleId)}` : RULES_PAGE_LINK, | |||
alertDetails: (alertId?: string | null) => | |||
alertId ? `${ALERT_PAGE_LINK}/${encodeURI(alertId)}` : ALERT_PAGE_LINK, | |||
alertDetails: (alertId?: string | null, ruleId?: string | null) => |
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.
@benakansara, alertId
and ruleId
should not be optional arguments. But the PR is already merged
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.
@fkanout agreed, I think there is no use case where alertDetails() will be called without parameters. But in case it does, user will be redirected to Alerts page. It will not break the page. For code clarity, I agree to not make it optional. I will include this change in another PR.
Summary
Part of #139269
This PR is only for creating alert details page link with alert id and rule id.