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

Deep relations: wrong type behavior #156

Open
LaKrue opened this issue Apr 16, 2013 · 2 comments
Open

Deep relations: wrong type behavior #156

LaKrue opened this issue Apr 16, 2013 · 2 comments

Comments

@LaKrue
Copy link

LaKrue commented Apr 16, 2013

Only the root type is matched correctly if annotated deep relation source is initially parsed.
Subtypes are not correctly recognized as such (at least not correctly).

Adding children after the initial parsing does work as expected, but only work from the root type.

Referring to my linked examples:

  • All buttons below "Level1-1" are hidden by default and no types are recognized
  • Starting from the button "Add Level1 child" all (sub)types works as expected

The following two examples are based on the VIE "deep relation" test case (see source).

@LaKrue
Copy link
Author

LaKrue commented Apr 22, 2013

I just created example 1 on jsfiddle:
http://jsfiddle.net/LaKrue85/Pc9d9/

@bergie
Copy link
Owner

bergie commented Apr 26, 2013

If you have the time, would be great to get some unit tests to demonstrate this. Makes fixing easier :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants