Daniel, Joe, and Ryan chatted over Skype. Ryan was unavailable for 20 minutes in the middle of it. Rachel couldn’t make it.

• Main thing want to fix is that we get continual questions about meta.
• Ryan has made a doc change to explain why we don’t expose meta by default.
• Joe: Can we just go through and fix all of the bugs?
• Daniel: Some are fixable bugs, other are debatable bugs. Let’s rename “Feedback” to “Discussion” as an indicator for debatable bugs.
• Discussed DELETE requests https://github.com/WP-API/WP-API/issues/789
• Problem is that it’s inconsistent: calling DELETE twice shouldn’t have different behaviors.
• Ryan’s proposal: DELETE always trashes the post. force=true must be passed to permanently deleted.
• Discussed invalid arguments: https://github.com/WP-API/WP-API/issues/871
• Post format needs to be validated against a set of potential options.
• parent_id and author_id need to be validated against their respective objects
• post_title and post_content also should check string types because saving an object would be bad
• One potential implementation is some validate argument of the schema that is automatically checked before hitting create_item()
• Discussed read-only fields: https://github.com/WP-API/WP-API/issues/747
• Might be another argument for preflighting data so we can throw an error if you try to supply the field
• Possible rule to follow for the API: if invalid data has been provided for a valid field, throw an error. If invalid data has been provided for an invalid field, we can silently ignore.
• Joe and Daniel are generally against nested object for discussion. Count should be an attribute of the link to the collection, and it doesn’t make sense to have statuses for posts and pings. We should avoid nested objects as much as possible because they make for painful cURL requests.
• Title (raw|rendered) and content (raw|rendered) are unaddressed beasts in this regard. Some discussion of their inconsistencies.
• Discussed named routes: https://github.com/WP-API/WP-API/issues/577
• One useful use for this is shorthand for referring to other routes. Avoids having to update a bunch of paths.