This repository was archived by the owner on Apr 12, 2024. It is now read-only.
Added a comment on a misleading declaration on the $location guide #12987
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the guide is followed correctly, a seemingly innocuous $sniffer value is
set on the module. For the new developer this is pretty normal. But what is
completely hidden is that setting this value in that way, will silently prevent
all animations from ngAnimate.
Unless the developer knows that the value is not intended to be modified
(it's an internal service after all, it usually never is) they might
end up breaking their animations unknowingly.