[wp-trac] [WordPress Trac] #24152: Use JSON as alternative to headers

WordPress Trac noreply at wordpress.org
Mon Apr 22 04:35:47 UTC 2013


#24152: Use JSON as alternative to headers
-----------------------------+------------------------------
 Reporter:  ryanve           |       Owner:
     Type:  feature request  |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Themes           |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  close            |
-----------------------------+------------------------------
Changes (by nacin):

 * keywords:   => close


Comment:

 While this means you don't need a style.css file for a theme, you'll still
 need a .json file. Considering you don't actually need to use style.css
 for, well, CSS, this isn't much of a benefit. If anything, it means people
 will need to look in two places, not one. And given that all plugins do
 need a file, this will mean that plugins now need a minimum of two files.
 (Many plugins are very simple single-file plugins that can go into wp-
 content/plugins directly, and this is common for custom managed sites.)

 While JSON files are both machine-readable and human-readable, they aren't
 necessarily human-editable. You need to understand syntax and such, and
 there are some gotchas like trailing commas and when to quote that can be
 confusing. I think this would be a nice thing to keep in our back pocket
 in case the world of dependencies, testing, and such force something more
 powerful than the existing headers. But the current headers are a very
 integral part of WordPress and are one of those things that make things so
 simple to so many.

 Cool idea, but suggesting we close this as maybelater.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/24152#comment:6>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list