Fix extra fields on findings not saving - #660
Merged
chrismaddalena merged 1 commit intoAug 8, 2025
Merged
Conversation
The extra field was being set in the wrong place in the gql query data.
ColonelThirtyTwo
force-pushed
the
fix-finding-extra-field-edit
branch
from
August 8, 2025 14:10
6a35dae to
d139dc9
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #660 +/- ##
=======================================
Coverage 92.36% 92.36%
=======================================
Files 342 342
Lines 19611 19611
=======================================
Hits 18113 18113
Misses 1498 1498 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The extra field was being set in the wrong place in the gql query data.