Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
views.module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
19 Oct 2012 at 11:28 UTC
Updated:
29 Jul 2014 at 21:22 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
xjmHow about NodeView, etc.? That would match the names of the API functions.
Comment #2
damiankloip commentedHmm, I'm not sure. Me and @dawehener talked about this briefly yesterday and thought maybe NodeRow etc..
I personally think we should avoid using the word 'View' in these names. If we follow other core stuff, like field formatters, we should go with NodeRow, CommentRow...
Did a patch on the train. I also removed a random variable that somehow made it's way in the Entity class.
Comment #3
xjmI confirmed that this is the only reference to this variable in core (don't you love saying that??).
That naming pattern seems reasonable to me. I haven't checked everything over yet; are there really no references to these classes outside the class declaration? Maybe that's the beauty of annotated plugins.
Comment #4
damiankloip commentedYeah, It does keep things clean. It's all about that plugin ID! and of course it's the only reference to that variable :)
Comment #5
dawehnerI totally agree that these variable names help to understand the purpose of the file.
In general we should wait for a global renaming until short before code freeze.
Comment #6
xjmI'd actually disagree since it's just these few classes. The current names are really confusing.
Comment #7
dawehnerOh i talked about renaming all the other classes... this should wait but for that patch i totally agree that everything else is damn confusing.
Comment #8
webchickThis seems much clearer than before.
Committed and pushed to 8.x. Thanks!