Skip storing draft in RBF form, reintroduce precomposedForm #15402
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.
RBF form should not store transaction drafts. It creates confusion when send form is opened with unexpected pre-filled data and also causes errors when a transaction is created in thusly affected send form.
This PR reintroduces
precomposedForm
which holds similar data as drafts, but is used by both send form and RBF form synchronize data between the form and the review modal.These changes may affect the mobile app.
Related Issue
Resolve #13325
Resolve #14753 (create a transaction, , open RBF form, replace the transaction, go to send form, try to send)
Resolve #15114 (create a transaction, open RBF form, close it without replacing the transaction, go to send form, try to send)