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

Forward non-intercepted methods on class proxies to target #571

Merged

Commits on Feb 3, 2021

  1. Non-proxied methods should forward to target

    The (failing) tests being added here specify that if one chooses via
    `IProxyGenerationHook.ShouldInterceptMethod` not to intercept a method
    then invocations of that method on the proxy should be forwarded to
    the target object (if present).
    stakx committed Feb 3, 2021
    Copy the full SHA
    56d74dd View commit details
    Browse the repository at this point in the history
  2. Copy the full SHA
    41556e9 View commit details
    Browse the repository at this point in the history
  3. hook.ShouldInterceptMethod now broken for non-public methods

    Using `IndirectlyCalledMethodGenerator` for non-public methods even when
    `method.Proxyable == false` is wrong because it will cause interceptors
    to be invoked. But if the hook decided that a method shouldn't be inter-
    cepted, that is obviously wrong.
    stakx committed Feb 3, 2021
    Copy the full SHA
    aeb19c2 View commit details
    Browse the repository at this point in the history
  4. Copy the full SHA
    ea5b272 View commit details
    Browse the repository at this point in the history
  5. Update the changelog

    stakx committed Feb 3, 2021
    Copy the full SHA
    77743ac View commit details
    Browse the repository at this point in the history