我有公开课RuleInfo
它是从内部类创建的Rule
.
private static RuleInfo CreateRuleInfo(Rule r)
{
return new RuleInfo
{
RuleCode = r.RuleId,
DisplayName = r.RuleCode,
Description = r.Description,
LegacyRuleCode = null
};
}
它们的属性名称各不相同,因此ShouldBeEquivalentTo()
or ShouldAllBeEquivalentTo()
不工作。
现在我正在手动/显式比较它们:
foreach (var x in Enumerable.Zip(infs, rules, (i, r) => new { Info = i, Rule = r }))
{
x.Info.ShouldBeEquivalentTo(
new
{
RuleCode = x.Rule.RuleId,
DisplayName = x.Rule.RuleCode,
Description = x.Rule.Description,
LegacyRuleCode = (string)null
});
}
有没有更好、更紧凑、不那么明确、更易读的方式?
一种选择是将自定义等效步骤添加到全局选项配置中:
class DifferentObjectsEquivalencyStep<T1, T2> : IEquivalencyStep {
private readonly Func<T1, T2> _converter;
public DifferentObjectsEquivalencyStep(Func<T1, T2> converter) {
_converter = converter;
}
public bool CanHandle(IEquivalencyValidationContext context, IEquivalencyAssertionOptions config) {
return context.Subject is T1 && context.Expectation is T2 || context.Subject is T2 && context.Expectation is T1;
}
public bool Handle(IEquivalencyValidationContext context, IEquivalencyValidator parent, IEquivalencyAssertionOptions config) {
var first = context.Subject is T1 ? (T1) context.Subject : (T1) context.Expectation;
var second = context.Subject is T2 ? (T2) context.Subject : (T2) context.Expectation;
second.ShouldBeEquivalentTo(_converter(first));
return true;
}
}
然后在进行所有比较之前的某个地方:
AssertionOptions.AssertEquivalencyUsing(c => c.Using(
new DifferentObjectsEquivalencyStep<Rule, RuleInfo>(CreateRuleInfo)));
之后,定期ShouldBeEquivalentTo
(and ShouldAllBeEquivalentTo
) 将工作:
rule.ShouldBeEquivalentTo(info);
本文内容由网友自发贡献,版权归原作者所有,本站不承担相应法律责任。如您发现有涉嫌抄袭侵权的内容,请联系:hwhale#tublm.com(使用前将#替换为@)