[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 dd32):

 At first, this doesn't seem like a great direction for WordPress.com to go
 in, as it appears to me that it would perhaps diverge the API and cause
 incompatibilities with clients written for the .org API vs .com API (even
 when using the same API effectively).
 Just thinking out loud here, I have a feeling a bunch of API clients are
 going to expect that they can take the root path element to the API and
 then suffix routes on from there. It also makes me question it'd possibly
 limit future uses of the API in plugins/etc (ie. Does it become `/my-
 plugin/v1/sites/123456/my-endpoint` when eventually supported? Etc)

 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?

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