Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

Update ngIf.js doc. Added missing description of ng-if behavior. #7776

Closed
wants to merge 3 commits into from
Closed

Update ngIf.js doc. Added missing description of ng-if behavior. #7776

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ae058df
Update ngIf.js
tuchk4 Jun 10, 2014
bb60f8b
Update ngIf.js
tuchk4 Jun 11, 2014
ce2d755
Update ngIf.js
tuchk4 Jun 11, 2014
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions src/ng/directive/ngIf.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,11 @@
* case when this difference is significant is when using css selectors that rely on an element's
* position within the DOM, such as the `:first-child` or `:last-child` pseudo-classes.
*
* <div class="alert alert-warning">
* **Note:** Here is a list of values that ngShow will consider as a falsy value (case insensitive):<br />
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It still says ngShow here instead of ngIf.

* "f" / "0" / "false" / "no" / "n" / "[]"
* </div>
*
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

trailing whitespace

* Note that when an element is removed using `ngIf` its scope is destroyed and a new scope
* is created when the element is restored. The scope created within `ngIf` inherits from
* its parent scope using
Expand Down