Repository navigation
Fix: only refuse a requirements save when the files' content changed - #355
Merged
Merged
Conversation
The editor refused to save when requirements.json or traceability.json had a newer modification time than when it was loaded. VectorCAST rewrites requirements.json with identical content when it runs a test, exports a test script or marks a test reviewed, so after any of those the next save was refused and the user had to reopen the view and redo their edits. Compare a hash of each file's content instead. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #355 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 12 12
Lines 2349 2349
Branches 329 329
=========================================
Hits 2349 2349
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Den1552
approved these changes
Nov 9, 2026
|
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 requirements editor refused to save ("changed on disk since it was loaded") whenever requirements.json was newer than when the editor opened it. But VectorCAST rewrites that file with exactly the same content when it runs a test, exports a test script or marks a test reviewed, so after almost any VectorCAST action the next save failed and you had to reopen the editor and redo your edits. The editor now compares the files' content instead of their timestamps, so it still refuses when someone really changed them.