- Issue created by @arunkumark
- @arunkumark opened merge request.
- Issue was unassigned.
- Status changed to Needs review
almost 2 years ago 4:59am 13 February 2023 - 🇮🇳India arunkumark Coimbatore
Created the merge request to resolve the coding standard issue.
- 🇮🇳India nayana_mvr
Verified the patch #3 on Drupal version 9.5.x and Commerce View Receipt version 1.0.x. The patch applied cleanly but there is still one minor issue
FILE: ../commerce_view_receipt/commerce_view_receipt.module --------------------------------------------------------------------------------------------------------------------- FOUND 1 ERROR AFFECTING 1 LINE --------------------------------------------------------------------------------------------------------------------- 15 | ERROR | [x] Expected 1 newline at end of file; 2 found --------------------------------------------------------------------------------------------------------------------- PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY --------------------------------------------------------------------------------------------------------------------- FILE: ../commerce_view_receipt/README.txt --------------------------------------------------------------------------------------------------- FOUND 1 ERROR AFFECTING 1 LINE --------------------------------------------------------------------------------------------------- 34 | ERROR | [x] Expected 1 newline at end of file; 2 found --------------------------------------------------------------------------------------------------- PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY ---------------------------------------------------------------------------------------------------
I think README.txt file issue can be ignored as it will be replaced with README.md as per ticket 3341190 📌 Replace README.txt with README.md and update README.md file Fixed
- First commit to issue fork.
-
gregcube →
committed fc17513a on 1.0.x authored by
arunkumark →
Issue #3341188: PHP Coding standard issue
-
gregcube →
committed fc17513a on 1.0.x authored by
arunkumark →
- Status changed to Fixed
almost 2 years ago 11:24pm 27 February 2023 Automatically closed - issue fixed for 2 weeks with no activity.