-
Notifications
You must be signed in to change notification settings - Fork 630
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #53 from fronn/patch-1
Fix for issue #52
- Loading branch information
Showing
1 changed file
with
18 additions
and
12 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
82e5d17
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change caused my app to not be able to initialize successfully, as it could not resolve route.authRequired - it seems it is not being passed $route.current correctly, why could this be the case?
82e5d17
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
current
is null for me occasionally. I think it's just on the initial calls, where there actually is no existing route. Could you be running into this use case?82e5d17
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Having debugged the code, I believe so - I was able to get my tests (and the live page) to pass by changing the code to:
I have made the assumption that options.path is the same route as the initial load. I am wondering if there is a more elegant solution so will be opening a new issue to discuss.