[wp-trac] [WordPress Trac] #38490: Add settings to the `/wp/v2/settings` endpoint that are in the WordPress.com api

[WordPress Trac]

#38490: Add settings to the `/wp/v2/settings` endpoint that are in the
WordPress.com api
-----------------------------------------+-----------------------
 Reporter:  joehoyle                     |       Owner:  joehoyle
     Type:  task (blessed)               |      Status:  assigned
 Priority:  normal                       |   Milestone:  4.7
Component:  REST API                     |     Version:
 Severity:  normal                       |  Resolution:
 Keywords:  has-patch reporter-feedback  |     Focuses:
-----------------------------------------+-----------------------

Comment (by joehoyle):

 > Should we add an easier way to include settings as read-only? If so, how
 can clients know whether or not they can write to a given setting?

 I don't think so no - an unsettable setting is a misnomer IMO. It may have
 a place in the API, but if it's informational, and not settable it
 shouldn't be in the settings endpoint. We have a way to markup read-only
 via the schema easily, which is what we do for all other fields, I just
 don't think it makes sense for an endpoint is which specifically for
 changing things.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/38490#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform