-
Notifications
You must be signed in to change notification settings - Fork 5k
Fix the default value of search record if the filter is boolean type #17297
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
base: main
Are you sure you want to change the base?
Conversation
Greptile SummaryThis PR adds default value handling for BOOLEAN type filters in the Context: This fixes issue #15896 where automation iterators with "search for record" filters on boolean fields would return the same record repeatedly after it was updated. The issue occurred because the boolean filter didn't have an initial default value, causing incorrect filter behavior. How it works: The fix adds a case for Confidence Score: 5/5
Important Files Changed
|
Greptile's behavior is changing!From now on, if a review finishes with no comments, we will not post an additional "statistics" comment to confirm that our review found nothing to comment on. However, you can confirm that we reviewed your changes in the status check section. This feature can be toggled off in your Code Review Settings by deselecting "Create a status check for each PR". |
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.
No issues found across 1 file
|
🚀 Preview Environment Ready! Your preview environment is available at: http://bore.pub:62738 This environment will automatically shut down when the PR is closed or after 5 hours. |
…x-Search-Record-Issue
d293be7 to
63b65d7
Compare
This fixes the #15896. For problem statement. Please refer to the shared video mentioned in the issue.