Testing changes from issue #1028 (conditionals with ../)

[martiniert]

Currently I'm still using old handlebars version 3.0.0 because I've got a huge project with over 700 instances of "../".
In handlebars 4.0.0, the issue #1028 was fixed, therefore all instances of ../ within conditionals need to be retested.

Is there a another way to test the behaviour of the conditional context switches then just clicking through the whole project by hand?
Is is possible to give a console warning where the ../ now behaves differently than before?

[jaylinski]

I'm afraid you have to write tests for your application in order to find out about broken templates after upgrading to v4.

Another possibility would be to use a custom version of handlebars.js v4, where you would insert console.warning() in the two places touched by this commit: 279e038