-
Notifications
You must be signed in to change notification settings - Fork 475
Fixes log alert query not saving #6633
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
Conversation
…e function to be more clear
2935b4a to
68e2d70
Compare
SpennyNDaJets
left a comment
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.
Code and click test look good to me!
|
@anthonygregis linter seems to be failing could you run |
|
Sorry about that, will run and push up |
|
@anthonygregis no worries. looks like the yarn.lock changes are local to your project, do you mind removing that from your PR? |
|
@Vadman97 @SpennyNDaJets Will fix yarn.lock issue now, most likely happened because I'm on Windows. |
## Summary This resolves an issue when defining a log alert query. When a user inputs a log query the value was being set into a local variable to update the histogram but was not updating the formStore that was being used to populate the mutation input variables. This PR should resolve this issue and allow for query to be sent along to the mutation. Related Issue: highlight#6630 ## How did you test this change? Test both locally and in self deployed version ## Are there any deployment considerations? None, purely frontend changes ## Does this work require review from our design team? No --------- Co-authored-by: Anthony Gregis <agregis@dustlabs.com> Co-authored-by: TheBasedBob <bob@degods.com>
Summary
This resolves an issue when defining a log alert query. When a user inputs a log query the value was being set into a local variable to update the histogram but was not updating the formStore that was being used to populate the mutation input variables. This PR should resolve this issue and allow for query to be sent along to the mutation.
Related Issue: #6630
How did you test this change?
Test both locally and in self deployed version
Are there any deployment considerations?
None, purely frontend changes
Does this work require review from our design team?
No