[wp-trac] [WordPress Trac] #38342: Quick Draft: Leverage REST API endpoints
WordPress Trac
noreply at wordpress.org
Sun Nov 20 21:53:16 UTC 2016
#38342: Quick Draft: Leverage REST API endpoints
---------------------------------+-----------------------------------
Reporter: adamsilverstein | Owner: joehoyle
Type: enhancement | Status: assigned
Priority: normal | Milestone: Future Release
Component: Administration | Version:
Severity: normal | Resolution:
Keywords: has-patch 4.8-early | Focuses: javascript, rest-api
---------------------------------+-----------------------------------
Comment (by adamsilverstein):
@joehoyle thanks for taking this up! I like the direction of your latest
patch and will test it out... I would like to work towards getting actual
gmt data in the database (and api response), thanks for opening #38883.
@aduth makes a good point that we still are losing potentially useful
hooks. Long term, we need to think more here about forward compatibility
than backward compatibility. That is ''if we deprecate a filter or hook
developers use in PHP, can we provide a similar standard approach for
developers to use in our new JavaScript application''? Once we have
standard JavaScript actions and filters (#21170) we can include
matching/similar JavaScript filters for `wp_trim_words`,
`get_edit_post_link` and even `dashboard_recent_drafts_query_args`.
@jnylen0 Thanks for the feedback, the use of `wp_localize_script` seems
reasonable here since this client lives in the admin. I agree reading site
settings just to figure out a proper date is not ideal.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/38342#comment:53>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list