User tests: Successful: Unsuccessful:
Code review.
Status | New | ⇒ | Pending |
Category | ⇒ | Administration Templates (admin) NPM Change |
I have tested this item
Status | Pending | ⇒ | Ready to Commit |
Labels |
Added:
?
NPM Resource Changed
|
RTC.
Status | Ready to Commit | ⇒ | Pending |
Sorry, setting back to pending. Tests are failing. The file is still referenced in administrator/templates/atum/scss/vendor/choicesjs/choices.scss
Good spot. Annoyed I missed that
Labels |
I have tested this item
So as we can see, a code review is NOT sufficient to test such PRs. It needs to run npm to see if scss files are still compiled without errors, or at least to check drone.
And if code review, then a simple findstr /s /c:"../mixin" *.scss
in a Windows command shell or find ./ -type f -name "*\.scss" -exec grep -Hn "../mixin" {} \;
in a Linux shell would have shown the remaining imports, too.
Code review doesn't mean to look only on the changes in a PR, it means also e.g. if something is removed from code to make sure it is not used anywhere else.
Status | Pending | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2021-07-14 15:46:46 |
Closed_By | ⇒ | Quy |
I have tested this item✅ successfully on 5336a21
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/31210.