-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: place imported assets to correct class #2409
feat: place imported assets to correct class #2409
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## develop #2409 +/- ##
==========================================
Coverage 16.71% 16.71%
Complexity 3182 3182
==========================================
Files 207 207
Lines 11453 11453
==========================================
Hits 1914 1914
Misses 9539 9539
☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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 is respecting code style rules
- New code is respecting 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
- Changelog is updated according to changes (if applicable)
- Documentation is updated according to changes (if applicable)
Version
There are 0 BREAKING CHANGE, 1 feature, 0 fix |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- New code is covered by tests (if applicable)
- Tests are running successfully (old and new ones) on my local machine (if applicable)
- New code is respecting code style rules
- New code is respecting 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
@@ -96,6 +96,9 @@ class taoQtiTest_models_classes_QtiTestService extends TestService | |||
public const XML_TEST_PART = 'testPart'; | |||
public const XML_ASSESSMENT_SECTION = 'assessmentSection'; | |||
public const XML_ASSESSMENT_ITEM_REF = 'assessmentItemRef'; | |||
|
|||
private const IN_PROGRESS_LABEL = 'in progress'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think LABEL_IN_PROGESS is better, because then you would just add another LABEL_ and everything would be in same code block
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The text for the label when status is in progress: 'in progress' status label IN_PROGRESS_LABEL
For me sounds more clear than: label for 'in progress' status - more context dropped
Ticket: https://oat-sa.atlassian.net/browse/PISA25-561
What's Changed
Related PR: oat-sa/extension-tao-itemqti#2407
How to test
check: oat-sa/extension-tao-itemqti#2407