This repository was archived by the owner on Sep 24, 2018. It is now read-only.
Rename register_api_field() to register_rest_field()#1824
Merged
Conversation
Introduces a `register_api_field()` function for backwards compat, which calls `_doing_it_wrong()`
Member
Author
|
@WP-API/amigos #reviewmerge |
Member
|
@danielbachhuber are you thinking the backcompat function will also go into core when the time comes? |
joehoyle
added a commit
that referenced
this pull request
Dec 10, 2015
Rename `register_api_field()` to `register_rest_field()`
Member
Author
Nope. We can keep it in the plugin indefinitely. If the user has the plugin activated, then they'll be able to use the function. When they deactivate the plugin, they should update function calls. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduces a
register_api_field()function for backwards compat, whichcalls
_doing_it_wrong()Fixes #1321