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
@Krinkle is introducing Karma to the jQuery test suite, and it looks like our custom context file will be fairly complex. To avoid code duplication, I'd like to reuse it for a custom debug file, but we cannot because there's apparently no documented way to detect that it's being used for debug.
Expected behaviour
Something like an %IS_DEBUG%directive that gets replaced with true or false so debug-specific processing can happen dynamically.
Actual behaviour
We have to use something like /^[/]debug\b/.test(location.pathname), but I don't think /debug.html is actually part of your public API (though it is mentioned on the troubleshooting page).
The text was updated successfully, but these errors were encountered:
This seems simple enough. Doing an additional replace when pages are served and replacing %IS_DEBUG% with the value of isRequestingDebugFile might do the trick, since that value tracks whether the location is debug.html.
@Krinkle is introducing Karma to the jQuery test suite, and it looks like our custom context file will be fairly complex. To avoid code duplication, I'd like to reuse it for a custom debug file, but we cannot because there's apparently no documented way to detect that it's being used for debug.
Expected behaviour
Something like an
%IS_DEBUG%
directive that gets replaced withtrue
orfalse
so debug-specific processing can happen dynamically.Actual behaviour
We have to use something like
/^[/]debug\b/.test(location.pathname)
, but I don't think/debug.html
is actually part of your public API (though it is mentioned on the troubleshooting page).The text was updated successfully, but these errors were encountered: