[wp-trac] [WordPress Trac] #9674: Better support for custom post types
WordPress Trac
wp-trac at lists.automattic.com
Thu Dec 31 20:45:24 UTC 2009
#9674: Better support for custom post types
------------------------------------+---------------------------------------
Reporter: wnorris | Owner: ryan
Type: task (blessed) | Status: reopened
Priority: normal | Milestone: 3.0
Component: Administration | Version: 2.9
Severity: normal | Resolution:
Keywords: has-patch tested early |
------------------------------------+---------------------------------------
Comment(by azaozz):
Replying to [comment:89 ryan]:
> I'm going to take a cue from my sample plugin and use "thingy"
everywhere. get_thingy_type(). Who's with me? ;-)
+1. Hmm, so we will have "thingy", thingies", "thingomery"? :-)
Seriously though, don't forget we are talking about an API that is seen
only by developers and each function has phpdoc description. It's nice to
have descriptive names but it's imperative to have a well thought and well
written API.
IMHO all of these would work well: "post" (current), "object" (a bit too
generic), "content" (yes, content_type is also a HTTP header but that's
completely different scope).
From a non-developer's point of view "content" seems to make the most
sense. It is the content of the web site. From developer's point of view,
it doesn't really matter that much as long as it works well and is
documented.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/9674#comment:93>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list