fix: delete outcomes if no responses set #2549
Merged
Conversation
This file contains 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
Front-end summary Node 18
|
jsconan
approved these changes
Jul 17, 2024
There was a problem hiding this comment.
Review Checklist
- New code is covered by tests (if applicable)
- Tests are running successfully (old and new ones) on my local machine (if applicable)
- New code respects code style rules
- New code respects best practices
- New code is not subject to concurrency issues (if applicable)
- Feature is working correctly on my local machine (if applicable)
- Acceptance criteria are respected
- Pull request title and description are meaningful
- Pull request's target is not
master - Commits are following conventional commits
- Commits messages are meaningful
- Commits are atomic
Karol-Stelmaczonek
approved these changes
Jul 17, 2024
Version
There are 0 BREAKING CHANGE, 0 feature, 4 fixes |
viktar-dzmitryieu-tao
deleted the
fix/AUT-3735/delete-outcomes-if-no-responses-set
branch
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.
Ticket: https://oat-sa.atlassian.net/browse/AUT-3735
Fixed the issue when after deleting of an interaction which was contained responses and custom outcome declarations, they will be not deleted properly and will generate inconsistency inside XML
What's Changed
How to test
Appropriate PR in the npm package: oat-sa/tao-item-runner-qti-fe#409
Deployed to https://construct1-oat-unit07.dev.gcp-eu.taocloud.org/tao/Main/login