Closed kadamwhite closed 4 years ago
All in favour of this! Will make things easier to manage on a PR and issue stand point.
I work make a quick post on make blog and draw eyes to the work already done the menus apis.
@spacedmonkey Sounds good. Let me know when you have a draft of that ready, I was writing a similar post for next week and we can combine our efforts :)
I am travelling at the moment with limited wifi and computer access. I will not be able to do anything until I get back on 9th of August.
My recommend the following.
I have done exactly as suggested, except I omitted the redundant wp-api-
prefix. wp-api/widgets-endpoints now exists; PR to remove widget content from this repo to follow.
AFAICT everything has been actioned here.
On August 6 I intend to rename this repository to
wp-api/menus-endpoints
and create a new repositoriy from the same HEAD calledwp-api/widgets-endpoints
.I then intend to remove all widget-related code & documentation from the menus endpoints plugin, and vice-versa
This will entail closing some open PRs of @BE-Webdesign's, as we'd be re-purposing this repository to focus on @spacedmonkey's recent work to solidify the menus endpoints for use in Gutenberg. As those PRs are all somewhat outdated I don't foresee this being an issue, but we can re-open them on the new repository or add an issue back-linking to the closed PRs.
33 will be invalidated, but we're waiting on feedback on the intend of that change so closing it pending provisionally moving it to the new repository should be similarly feasible.
Please comment below if you have an argument against this proposal; silence or positively-connoted emoji reactions will be interpreted as support :)