Repository navigation
Comparing changes
Open a pull request
base repository: WP-API/WP-API
base: develop
head repository: tobych/WP-API
compare: users
- 15 commits
- 4 files changed
- 1 contributor
Commits on Apr 8, 2014
-
Add beginnings of user endpoint based on @royboy789's work
Works; incomplete; no unit tests.
Configuration menu - View commit details
-
Copy full SHA for 442a403 - Browse repository at this point
Copy the full SHA 442a403View commit details -
Configuration menu - View commit details
-
Copy full SHA for df9ada3 - Browse repository at this point
Copy the full SHA df9ada3View commit details -
Add edit_user (still no DELETE or POST handling)
Only some fields. I'm testing this from a Python client, so still no unit tests in PHP.
Configuration menu - View commit details
-
Copy full SHA for dd25eaf - Browse repository at this point
Copy the full SHA dd25eafView commit details -
Configuration menu - View commit details
-
Copy full SHA for 49d96aa - Browse repository at this point
Copy the full SHA 49d96aaView commit details -
Configuration menu - View commit details
-
Copy full SHA for d32e5b9 - Browse repository at this point
Copy the full SHA d32e5b9View commit details -
Configuration menu - View commit details
-
Copy full SHA for d1af273 - Browse repository at this point
Copy the full SHA d1af273View commit details -
Configuration menu - View commit details
-
Copy full SHA for 23babbc - Browse repository at this point
Copy the full SHA 23babbcView commit details -
Configuration menu - View commit details
-
Copy full SHA for 4e84b48 - Browse repository at this point
Copy the full SHA 4e84b48View commit details -
Configuration menu - View commit details
-
Copy full SHA for 937e7e3 - Browse repository at this point
Copy the full SHA 937e7e3View commit details -
Handle user meta data better, including serialized values
- meta values are always represented as arrays - serialized values are represented as dictionaries with 'unserialized' and 'serialized' keys. only 'unserialized' is used when you update. - if you send it a single value, it makes it into an array (to be kind) - doesn't deal with multiple values coming back yet (see comments)
Configuration menu - View commit details
-
Copy full SHA for 7ea0724 - Browse repository at this point
Copy the full SHA 7ea0724View commit details -
Configuration menu - View commit details
-
Copy full SHA for d447bad - Browse repository at this point
Copy the full SHA d447badView commit details -
Configuration menu - View commit details
-
Copy full SHA for b504dba - Browse repository at this point
Copy the full SHA b504dbaView commit details -
Refactor a little and add commented-out code for single items
We could return user_meta values that have one item as a simple value rather than an array. Refactored tomake this easy, but it could probably cause problems further down the line and perhaps complicates things, so let's leave it to clients to deal with this.
Configuration menu - View commit details
-
Copy full SHA for 43e3c34 - Browse repository at this point
Copy the full SHA 43e3c34View commit details -
Get my User entity in line with the existing schema
This also removes any duplication between user_meta and non-user_meta.
Configuration menu - View commit details
-
Copy full SHA for b173cea - Browse repository at this point
Copy the full SHA b173ceaView commit details -
Fix [] so it works on older versions of PHP
Also fix some coding style stuff.
Configuration menu - View commit details
-
Copy full SHA for d30d2b2 - Browse repository at this point
Copy the full SHA d30d2b2View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff develop...users