Skip to content

Do Not Emit Matching Members From an Interface #226

@JasonBock

Description

@JasonBock

Consider this code:

public interface RequestHandle<T>
    where T : class { }

public interface IRequestClient<TRequest>
    where TRequest : class
{
    RequestHandle<TRequest> Create(TRequest message);

    RequestHandle<TRequest> Create(object values);			
}

The current mock will have both methods implemented, but it shouldn't. The resulting methods are exactly the same, so in that case, Rocks should only emit one.

This was found on MassTransit.IRequestClient<>

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions