Tenant Resolver API

gistfile1.cs

	// 1. Return identifiers using out parameter

    public interface ITenantResolver<TTenant>
    {
        Task<TTenant> Resolve(string identifier, out string[] tenantIdentifiers);
    }

    // 2. Return ResolvedTenant object containing identifiers

    public interface ITenantResolver<TTenant>
    {
        Task<ResolvedTenant<TTenant>> Resolve(string identifier);
    }

    public class ResolvedTenant<TTenant> 
    {
    	public TTenant Tenant { get; set; }
    	public string[] Identifiers { get; set; }
    }

public interface ITenantResolver
{
    Task<TTenant> Resolve<TTenant>(string identifier);
}

public class Tenant : TTenant
{
  public IEnumerable<string> Identifiers {get;set;}
}

Out parameters are one of the banes of our universe. So therefore, I agree with nancy boy.

I was trying to avoid imposing a certain tenant structure so people could return whatever they like without having to implement any kind of interface or have a dependency on Saaskit.

That was for the reason for wrapping the tenant type in ResolvedTenant.

no out parameters. ever.