All geek questions in one place

How to examine the “Re-compose exception form”, what are the keys?

I am in a large project, first exposed to the Meteor, and I begin to do this very often. It will be difficult to track it to a certain fixation, as it seemed intermittent.

What is a fruitful approach to finding a problem? Is there anything in this exception that helps narrow it down? How can I execute / set breakpoints in / exclude Deps? All my fingerprints are automatic from mongo operations, or one from a var session, nothing is explicit.

thanks

https://gist.github.com/jimmack1963/6254452

+4
source share
2 answers

In my experience, this usually means that you have code failure inside the template. You use {{#each for something that is not an array or object, or some other no-no. If you really used Deps.autorun somewhere, presumably you will see your function in the stack trace; but if tracing is just a list of the main Meteor functions, it means that the problem is likely in the template or in one of its assistants.

+6
source

Source: https://habr.com/ru/post/1497517/

More articles:


All Articles