[wp-trac] [WordPress Trac] #42807: Add filter to modfiy wp.api versionString

[WordPress Trac]

#42807: Add filter to modfiy wp.api versionString
--------------------------+------------------------------
 Reporter:  mkaz          |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  REST API      |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by rmccue):

 Replying to [comment:1 dd32]:
 > I'm curious why the reverse wasn't taken instead here `public-
 api.wordpress.com/sites/1234/wp/v2/post` - Maybe explaining that reasoning
 would make it easier to understand the need for this filter?

 This is somewhat a case of "the horse has already bolted", but I
 definitely agree here. Namespaces are linked directly to routes living
 directly underneath them, and some forms of feature detection rely on this
 being the case. Modifying the namespace definitely isn't something that
 I'd like to encourage, since it's intended to be a name.

 Would it be feasible to change .com's API at this point though?

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