Improve muzzle check for constructors #4591
Merged
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.
Muzzle should fail if our helper class references a library base class constructor that's absent on the classpath. For example imagine that muzzle codegen has captured references to the following class hierarchy:
Helper extends LibraryBaseClass extends Object
, all with default no-arg constructors. Now, if the actualLibraryBaseClass
on the application classpath had a constructor that requires along
the muzzle check would still pass - because it would find the default constructor in theObject
class. This PR fixes muzzle so that it recognizes this situation.