Closed (duplicate)
Project:
Drupal core
Version:
8.1.x-dev
Component:
toolbar.module
Priority:
Minor
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
14 Apr 2012 at 21:04 UTC
Updated:
21 Sep 2015 at 11:53 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
fluxsauce commentedComment #2
fluxsauce commentedCompleted.
Comment #3
traviscarden commentedSee #1533202-4: Make config module pass Coder Review. :)
Comment #4
fluxsauce commentedSummarized, sorry about that.
Comment #5
jody lynnConfirmed that all changes are style only and are correct coding standards.
Comment #6
traviscarden commentedI'm sorry. Per the initiative, adding param/return datatypes will be handled in a separate issue, so those changes need to be removed from the patch. Additionally, there are still style issues to fix:
Be sure to be using the latest copy of the code sniffer, by the way. It moves fast. I always update mine via Git before running it.
Comment #7
albert volkman commentedParam/return datatypes removed. Additional coder issues addressed except for the first issue in toolbar-rtl.css. It looks correct to me, so possibly a false positive?
Comment #7.0
albert volkman commentedSummarizing work done
Comment #8
traviscarden commentedIssue status updated with latest drupalcs report.
Thank you, @Albert Volkman, you're right; both errors are false positives. Would you like to create issues for them and add links to them in the summary here?
Comment #9
albert volkman commentedSure thing-
http://drupal.org/node/1623442
Comment #10
jhodgdonI thought we weren't in agreement on the coding standard yet, regarding this change:
I'm also confused about these changes (two like this) -- why are they necessary/desirable?
Comment #11
traviscarden commentedOops. I'm sorry, @jhodgdon: that first one got by me.
As to the second one, drupalcs complains about CSS properties that aren't in alphabetical order.
Comment #12
jhodgdonAlphabetical CSS -- OK -- I see that on the CSS coding standards page: http://drupal.org/node/302199
Comment #13
fluxsauce commentedThat's why I haven't rolled any new patches recently, I thought this whole thing was postponed. Kind of frustrating, really, I do want to contribute.
Comment #14
fluxsauce commentedComment #14.0
fluxsauce commentedUpdated issue status.
Comment #15
mgiffordI think there's agreement on the coding standards now https://www.drupal.org/node/1886770
Comment #16
xjmThanks for all the work here so far. See #1518116-86: [meta] Make Core pass Coder Review. This issue is postponed until the meta issue is either closed or reopened.
Comment #17
tatarbjClosing in favor of #2571965: [meta] Fix PHP coding standards in core, stage 1. In this issue the coding standards will be fixed on a sniff-per-sniff basis rather than a module-per-module basis.