Closed (won't fix)
Project:
Drupal core
Version:
8.0.x-dev
Component:
documentation
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
15 Apr 2012 at 00:18 UTC
Updated:
29 Jul 2014 at 20:36 UTC
Jump to comment: Most recent
Comments
Comment #0.0
traviscarden commentedUpdated issue summary.
Comment #1
amrit_b commentedThose instructions are only for contrib themes/modules.
Comment #2
traviscarden commentedThanks. We should probably make a note on the Coding Standards page then, do you think?
By the way, we aren't supposed to move issues directly into closed (fixed)—we move them to "fixed" instead so they don't fall off people's issue dashboard, and the Project issue tracking system will close them automatically after two weeks of inactivity.
Thanks!
Comment #3
amrit_b commentedYeah definitely Travis, but I don't have permission to edit that page.. And sorry, I didn't know about the 'closed(fixed)' - thanks for the the info, will keep in mind now on wards.
Comment #4
jhodgdonCoding standards need to be discussed in the Drupal Core issue queue.
Comment #5
traviscarden commentedI don't think this requires much discussion. It seems clear at this point that core is not meant to follow the same rule that contrib modules are for namespacing global variables. I would suggest just making that clear in the coding standards. Perhaps something like this:
Comment #5.0
traviscarden commentedUpdated issue summary.
Comment #6
pwarn commentedSince this has been sitting without comment for so long, should the issue be closed?
It doesn't seem clear that there is any change needed. "name should start" doesn't say that the "name is required to start". So the current documentation can be left as is, since it indicates best practice.
If the core folks decide that the coding standard should be changed, this should be talked about by the folks doing the core development, but is not clear that this is a documentation issue until someone decides to change something in the requirements for core.
Comment #7
jhodgdonI don't even think we really have any global variables in Core in 8.x, so we probably do not need this issue at all.
Thanks for digging it up!