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
Using {strict: true } gives me a head's up for missing values, which I want, but I've noticed when a partial is the source of the error, tracing the problem is challenging:
Error{column: 24,description: undefined,endColumn: 40,endLineNumber: 8,fileName: undefined,lineNumber: 8,message: '"domain" not defined in undefined - 8:24',name: 'Error',number: undefined,}
Lots of useful information, but still a struggle to track down on more complex sites with lots of partials or generic variables in play.
My question is whether there's a way to trace errors to the particular partial, or whether there's a way to decorate the Error thrown with the name of the partial.
I'm hoping to put some effort into the code seeing if this is a dumb request, but if anyone has some wisdom to share I'd be obliged.
Thanks, and thanks for a fantastic product - I've used it for probably 8 years or more (is that possible?)
The text was updated successfully, but these errors were encountered:
Howdy; Long time lurker, first time poster! =) I couldn't find this issue with a number of searches, so I apologize if it's been raised.
I'm using
v4.7.6
on the server side, with this roughly for my instantiation:Using
{strict: true }
gives me a head's up for missing values, which I want, but I've noticed when a partial is the source of the error, tracing the problem is challenging:Lots of useful information, but still a struggle to track down on more complex sites with lots of partials or generic variables in play.
My question is whether there's a way to trace errors to the particular partial, or whether there's a way to decorate the Error thrown with the
name
of the partial.I'm hoping to put some effort into the code seeing if this is a dumb request, but if anyone has some wisdom to share I'd be obliged.
Thanks, and thanks for a fantastic product - I've used it for probably 8 years or more (is that possible?)
The text was updated successfully, but these errors were encountered: