This repository has been archived by the owner on Feb 20, 2023. It is now read-only.
Error when mocking abstract class with no abstract methods #22
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.
When mocking an abstract class with no abstract methods using
getMockForAbstractClass()
an error occurs:generateMock()
should allow$methods
to benull
. This indicates no methods should be mocked (see 977).This pull request fixes this by allowing
null
while still enforcing type hinting. For more info, see the first paragraph of type hinting.