When a wysiwyg configuration is exported with Features, the resulting file throws coding standards violations when scanned with the latest version of Coder:

FILE: ...rence/lib/features/custom/ppcm_faq/ppcm_faq.features.wysiwyg.inc
----------------------------------------------------------------------
FOUND 1 ERROR AFFECTING 1 LINE
----------------------------------------------------------------------
 13 | ERROR | [x] Inline comments must end in full-stops, exclamation
    |       |     marks, colons, question marks, or closing
    |       |     parentheses
----------------------------------------------------------------------
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
----------------------------------------------------------------------

This is because lines similar to this not ending in a period:

  // Exported profile: ppcm_faq_format
CommentFileSizeAuthor
#2 2724173-2.patch643 bytespfrenssen
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

pfrenssen created an issue. See original summary.

pfrenssen’s picture

pfrenssen
Location Sofia
CreditAttribution: pfrenssen commented
Status: Active » Needs review
FileSize
2724173-2.patch643 bytes
alexverb’s picture

alexverb CreditAttribution: alexverb as a volunteer commented
Status: Needs review » Reviewed & tested by the community

Good to commit.

  • TwoD committed 7e67d86 on 7.x-2.x authored by pfrenssen 
    - #2724173 by pfrenssen, alexverb: Fixed coding standards violation in...
TwoD’s picture

TwoD
Primary language Swedish
Location Sweden
CreditAttribution: TwoD as a volunteer commented
Status: Reviewed & tested by the community » Fixed

Thank you for fixing this.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.