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
The problem's down to this change in that _isCircularNavigationInProgress never actually gets set to false - it either doesn't exist, or it does but it's set to true. So the if block never gets executed any more.
The quick fix would be to revert this line back to what it was... @brian-learningpool was there any technical reason for this change or did it just seem a more robust check to you?
I'm happy to look at ensuring _isCircularNavigationInProgress is properly defined and always set to either true or false, this probably requires a fair amount more testing though...
The text was updated successfully, but these errors were encountered:
Hi @moloko, the _isCircularNavigationInProgress was causing problems with the plugin route. I think _isCircularNavigationInProgress, if it should be a boolean, for clarity should be be true or false. I should have ensured that in the original PR.
The other calls in handleRoute referring to arguments could also use args instead.
Converted _isCircularNavigationInProgress to a boolean on the router object.
Added the pruneArguments() function and tidied up the passing of arguments.
Also corrected some minor indentation issues.
PR #1460 has unfortunately stopped our pageIncompletePrompt extension from working
The problem's down to this change in that
_isCircularNavigationInProgress
never actually gets set tofalse
- it either doesn't exist, or it does but it's set totrue
. So theif
block never gets executed any more.The quick fix would be to revert this line back to what it was... @brian-learningpool was there any technical reason for this change or did it just seem a more robust check to you?
I'm happy to look at ensuring
_isCircularNavigationInProgress
is properly defined and always set to eithertrue
orfalse
, this probably requires a fair amount more testing though...The text was updated successfully, but these errors were encountered: