This repository was archived by the owner on Apr 12, 2024. It is now read-only.
docs(ngController): Fix priority value mentioned in the docs #9070
Conversation
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
The `@priority 500` part was missing from the ngDoc comment, thus the docs mentioned a priority of 0 (instead of the correct 500).
petebacondarwin
force-pushed
the
master
branch
from
02dc2aa to
fd2d6c0
Compare
|
lgtm |
jeffbcross
pushed a commit
that referenced
this pull request
Sep 23, 2014
The `@priority 500` part was missing from the ngDoc comment, thus the docs mentioned a priority of 0 (instead of the correct 500). Closes #9070 Conflicts: src/ng/directive/ngController.js
jeffbcross
pushed a commit
that referenced
this pull request
Sep 23, 2014
The `@priority 500` part was missing from the ngDoc comment, thus the docs mentioned a priority of 0 (instead of the correct 500). Closes #9070
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The
@priority 500part was missing from the ngDoc comment, thus the docs mentioned a priority of 0(instead of the correct 500).