You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have been using a deep hash model to determine if we can re-use constructor/method maps when performing re-validation. This failed when a parameter type was initially unavailable and then became available because the hash only considers the current class source and that of its superclasses/interfaces.
See comment in ApexDeclaration.resetMethodMapIfInvalid() for where the deep hash comparison used to be performed.
The text was updated successfully, but these errors were encountered:
We have been using a deep hash model to determine if we can re-use constructor/method maps when performing re-validation. This failed when a parameter type was initially unavailable and then became available because the hash only considers the current class source and that of its superclasses/interfaces.
See comment in ApexDeclaration.resetMethodMapIfInvalid() for where the deep hash comparison used to be performed.
The text was updated successfully, but these errors were encountered: