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.

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

Fix: Alert condition rendering #4258

Closed
wants to merge 2 commits into from
Closed

Fix: Alert condition rendering #4258

wants to merge 2 commits into from

Conversation

ranbena
Copy link
Contributor

@ranbena ranbena commented Oct 17, 2019

  • Bug Fix

Description

Since #4240 alert conditions are no longer represented by a textual description but by chars. This caused templating (notification template and alert default name) to render differently.

This is a fix for that.

_ Before Fix After Fix
Alert Edit Screen Shot 2019-10-17 at 14 01 22 Screen Shot 2019-10-17 at 13 59 40
Email Screen Shot 2019-10-17 at 14 03 45 Screen Shot 2019-10-17 at 14 03 52

(Yes, I know there's server-client code duplication #4187)

@ranbena ranbena self-assigned this Oct 17, 2019
Made getConditionText safer
@arikfr
Copy link
Member

arikfr commented Oct 17, 2019

I'm not sure this is worth the extra complexity. Does it feel that important?

@ranbena
Copy link
Contributor Author

ranbena commented Oct 17, 2019

I'm not sure this is worth the extra complexity. Does it feel that important?

Was thinking that while working on it but I'm undecided. Up to you @arikfr.

@ranbena
Copy link
Contributor Author

ranbena commented Oct 17, 2019

Maybe we can settle for fixing only the alert name and leave out template rendering.

Copy link
Collaborator

@kravets-levko kravets-levko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As for me, math operatiors (< / <= / etc.) are good enough. But maybe "human-oriented" names will work better for non-tech people. I approve this PR because code looks fine, but I let you and @arikfr to decide if it should be merged or not.

@ranbena
Copy link
Contributor Author

ranbena commented Oct 31, 2019

I'm not sure this is worth the extra complexity. Does it feel that important?

Closing due to public disinterest.

@ranbena ranbena closed this Oct 31, 2019
@guidopetri guidopetri deleted the alert-condition branch July 22, 2023 03:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants