-
Notifications
You must be signed in to change notification settings - Fork 641
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
parseAggregate error address? #1087
Comments
Do you render your template with |
env.render(path, ctx). And I tried both sync and async versions. |
Can you show full stack? The message is quite strange because if an error would happen during rendering, it has to contain line numbers and source. But in your case, it looks like a typo in your code, which happens before rendering even can begin. |
I've already found it - it was |
I'm not sure what you're doing differently, but you should get an address. For some reason, you even get a different error. For instance, with your example I'm receiving following error:
Note that it is |
Full stack:
not sure how can it help |
+1 Please, it's a very big problem to search the "needle" in the haystack. |
I have a fix for this that I'll be pushing out shortly. |
@3.1.2
So I have made an error somewhere, but the error doesn't tell me where. This is all I get.
I can find it manually, no problem, but it would be much easier if knew at least roughly where...
Thank you.
The text was updated successfully, but these errors were encountered: