Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate wpFunction and wpPassthruFunction #78

Merged
merged 21 commits into from
Feb 14, 2017

Conversation

johnpbloch
Copy link
Contributor

This is to fix #18

John P Bloch and others added 20 commits November 19, 2016 16:09
The library already requires version 4.3. There are now a few features of 4.3+ that we have needed in tests, and now in the library itself. Deprecating wpFunction proved to be far too difficult if we were to maintain backwards compatibility with 3.7, so we're updating the requirements to 4.3. We could have done 4.0, but most people using a version < 4.3 are going to be using 3.7 anyway. It's easier to consolidate the version requirements so as to avoid confusion and to decrease the likelihood that our tests will miss an integration issue by not being able to run on the lowest supported version of phpunit.
This will allow a test to fail naturally first (in the tearDown method), then get marked as risky after that.
@johnpbloch
Copy link
Contributor Author

@lkwdwrd bump

@johnpbloch
Copy link
Contributor Author

@lkwdwrd since this is approved, could you go ahead and merge it?

@lkwdwrd lkwdwrd merged commit ccba313 into dev Feb 14, 2017
stevegrunwell added a commit to stevegrunwell/revision-strike that referenced this pull request Feb 26, 2017
…sthruFunction() with passthruFunction(), as the original methods were deprecated.

Reference: 10up/wp_mock#78
@ericmann ericmann deleted the feature/deprecate-wp-prefixes branch May 27, 2017 04:31
@jeffpaul jeffpaul added this to the 0.2.0 milestone Sep 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants