Add success/failure actions support #764
Merged
Conversation
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
- Add QSuccessFailureAction type for S/F actions - Add successAction/failureAction fields to QAction - Parse S/F actions from WebView messages in ActionMapper - Implement S/F action execution in ScreenFragment - Backward compatibility: use default behavior (closeAll/none) for old screens DEV-485
- Remove QSuccessFailureAction type - SDK doesn't need it - SDK sends successEvent/failureEvent to WebView - WebView handles S/F action execution via existing action mechanism - Simplify SDK code by delegating S/F logic to No-Code screen DEV-485
SpertsyanKM
changed the title
Use any() matcher for timestamp instead of System.currentTimeMillis() to avoid race condition between save() call and verification.
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.
No description provided.