微风更改的ComplexType类的顺序 [英] Breeze Changing the Order of ComplexType Classes

问题描述

我试图加载一个的ComplexType属性（P2）正从一个物业的ComplexType（P1）（嵌套的ComplexType）调用。获取元数据后，我看到两个类都被认为是复合类型，但在breeze.debug

I am trying to load a "ComplexType" property (p2) that is being called from a ComplexType property (p1) (Nested ComplexType). After getting the metadata I see that both classes were recognized as complextypes, but in breeze.debug

toArray(schema.complexType)

它看到P1（外复杂类型）第一，所以当它试图解决其属性类型这是一个复杂类型，P2之一。它的阅读

it's seeing the p1 (outside complextype) first, so then when it tries to resolve one of its property type which is a complexType, p2. it's reading

var type = typeMap[qualTypeName];

和因为类型映射没有P2和okNotFound是假的，它抛出一个错误

and since "typeMap" doesn't have p2 and "okNotFound" is false, it's throwing an error

Uncaught Error: Unable to locate an 'Type' by the name: Address:#Domain

任何人都遇到了同样的问题？我缺少的东西很明显？有没有一种方法，我可以在MVC4的Web API告诉EFContextProvider创建元数据时，P2之前呈现p1的？

Anyone have run into the same problem? Am I missing something very obvious? Is there a way I can tell EFContextProvider in MVC4 Web API to render p1 before p2 when creating Metadata?

推荐答案

修改：这是一个错误，并为v 1.3.2已定

Edit: This was a bug and as of v 1.3.2 has been fixed.

这可能是一个错误。我们没有嵌套复杂类型广泛的测试。我会尽量在今天或明天一早确认。

This may be a bug. We have not tested extensively with nested complex types. I will try to confirm it today or tommorow.

这篇关于微风更改的ComplexType类的顺序的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！