This repository was archived by the owner on Sep 24, 2018. It is now read-only.
Introduce edit context for Terms controller
#2230
Merged
Conversation
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
While `edit` doesn't include additional fields, it gives us a paradigm for adding `edit`-specific data in the future, and makes Terms more consistent with other controllers.
|
@WP-API/amigos #reviewmerge |
joehoyle
added a commit
that referenced
this pull request
Feb 4, 2016
Introduce `edit` context for Terms controller
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
While
editdoesn't include additional fields, it gives us a paradigmfor adding
edit-specific data in the future, and makes Terms moreconsistent with other controllers.
See #1845