You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I followed the recursive queries example from the book and I ran into issues when I put it together with the dynamic router.
Reproduction
When you navigate via the dynamic router to a component that has a recursive query, it throws the error:
Error: ... is not ISeqable
The component is rendered correctly when it's on the first rendered page but when you navigate to another page, and then back, it throws the error preventing the navigation.
See this behavior in the gif below:
If you comment out this line, turning off the recursive query, the error disappears and navigation works again, but then the recursive query is gone and only the top element is displayed.
Both recursive queries and dynamic router are great features and I'd love to use them together.
Maybe I'm not using them correctly but then again, I tried to follow the book as closely as possible.
Let me know if I could help you in some way with debugging this issue.
The text was updated successfully, but these errors were encountered:
Ah, this is not a dynamic router issue. The tx processing system isn't supporting recursive queries as written...I'll take a look at that.
awkay
changed the title
Recursive queries throw Error: ... is not ISeqable when navigating via dynamic router
Recursive queries cause errors in transaction processing when used with remotes
Aug 21, 2019
awkay
changed the title
Recursive queries cause errors in transaction processing when used with remotes
Recursive queries cause errors in comp/set-query*Aug 21, 2019
Hey,
I followed the recursive queries example from the book and I ran into issues when I put it together with the dynamic router.
Reproduction
When you navigate via the dynamic router to a component that has a recursive query, it throws the error:
The component is rendered correctly when it's on the first rendered page but when you navigate to another page, and then back, it throws the error preventing the navigation.
See this behavior in the gif below:
If you comment out this line, turning off the recursive query, the error disappears and navigation works again, but then the recursive query is gone and only the top element is displayed.
Stack trace from https://github.com/roterski/fulcro3-book
Stacktrace from my other project forked from fulcro3-template (maybe a more readable timbre trace)
Both recursive queries and dynamic router are great features and I'd love to use them together.
Maybe I'm not using them correctly but then again, I tried to follow the book as closely as possible.
Let me know if I could help you in some way with debugging this issue.
The text was updated successfully, but these errors were encountered: