Problem/Motivation

  • Currently, many Views plugin classes violate core naming standards in that the class's purpose is ambiguous when the namespace is not used. Reference: http://drupal.org/node/608152

Proposed resolution

  • Determine new standards for Views plugin naming so that the plugin's class name is more meaningful out of context.
  • Later in the release cycle, rename classes according to the new standard.

Comments

dawehner’s picture

dawehner
Primary language German
commented

I'm really sure not about the best way for naming views classes in both a consistens and useful way.
Let's take the Node field handler as example:

  • Node.php - That's the current name
  • FieldNode.php - Seems to remind to much on the fieldapi field?
  • ViewsFieldNode.php - Now we basically have covered nearly the full namespace, which will annoy people if they look into these directories.
xjm’s picture

xjm
she/her
Primary language English
commented
Status: Postponed » Closed (won't fix)
Issue tags: -Novice

We never really got consensus on a naming pattern and it's way past API freeze, so marking wontfix.