GROOVY-11823: try super.propertyMissing(name) before outer class
#2360
+65
−9
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.
I'm on the fence about this one. On the off chance an inner class' super class provides "methodMissing" or "propertyMissing", all inner class non-static dispatch methods need to call
super.methodMissing(name,args)orsuper.propertyMissing(name)orsuper.propertyMissing(name,value). The super class must throw a MissingMethodException or MissingPropertyException for the caller to be able to fall back on current behavior.The "ignore" exception could be thrown for no super class "methodMissing" or no "name" support, which is not ideal. In the event the super class does not supply "methodMissing", there is a call to this method which is why a guard was added (to prevent stack overflow). :(