fix: save condition on operator change in PolicyCondition.vue #1263
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.
Description
Fix policy condition operator changes not being saved automatically. Added missing change event handler to the operator dropdown to trigger
saveCondition()
when the operator value is modified, ensuring consistency with subject and value field behavior.Addressed Issue
Fixes #[508] - Policy condition operator changes not being saved
Solution: Added
v-on:change="saveCondition"
to the operator select component, matching the pattern used by other form fields in the component.Technical Details:
saveCondition()
already handles operator changes correctlyBefore: Operator changes required modifying another field to trigger save
After: Operator changes are saved immediately upon selection
Checklist
This PR introduces new or alters existing behavior, and I have updated the [documentation](https://github.com/DependencyTrack/dependency-track/tree/master/docs/_docs) accordingly(No documentation changes needed - this is a bug fix that restores expected behavior)