Merged
Conversation
Collaborator
@jarednova @gchtr I think we're ready to delete these. Of the remaining two tests in |
added 5 commits
October 29, 2020 14:20
This takes advantage of the fact that Post::init() only ever receives a WP_Post object, thanks to Factories. As a result we can eliminate many code paths that defend against not having a fully fledged WP_Post.
Member
Author
|
@acobster looks like versions of both had actually been ported over to |
Collaborator
|
SO SATISFYING. 🎉 🔪 |
Member
Author
|
It's like losing fifty pounds, right? (or 1865 lines of code I guess) |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Ticket: #2323
Issue
Remove the classes we identified in #2323
PostGetter... and tests
TermGetter... and tests
Any old
$CommentClassprops and the likeQueryIterator... and tests
Timber_WP_CLI_Command.php(or move to its own repo)Post::determine_id()and possibly other methodsSolution
Delete the classes. Ensure that Factories and other 2.x mechanisms are fully functional without these.
Usage Changes
Everything in 2.x
Considerations
It's been well considered
Testing
Interested to see how this affects coverage score. Looking to bring that back up to come close to current 1.x levels