Repository navigation
fix(financial-terms): preserve saved values when editing - #969
Merged
thlpkee20-wq merged 1 commit intoOct 22, 2026
Merged
Conversation
|
@Tonychris127 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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.
Overview
After saving financial terms, clicking Edit terms previously dispatched a reset and erased all six fields. Edit now returns to the populated form, allowing a user to change one value and save again. The explicit Reset action still clears the form.
Related Issue
Closes #919
Changes
Verification Results
npm run build: passed (the check enforced by CI).git diff --check: passed.Local validation used Node 24.21.0. An isolated dependency install hit the machine's disk-space limit; tests/build used the existing installation with an identical package-lock hash, with test discovery and generated outputs scoped to this checkout. No dependency or lockfile changes are included. The repository-wide test suite was not rerun for this focused change.