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
{{ message }}
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
"If we had not set the default value here, the model would stay uninitialized until our user picks an option from the drop down menu."
But then you go down to the experiments section and it says this:
"In the PhoneListCtrl controller, remove the statement that sets the orderProp value and you'll see that Angular will temporarily add a new "unknown" option to the drop-down list and the ordering will default to unordered/natural order."
This contradicts the earlier statement. The experiment text is correct, but the first statement leads you to believe that Angular won't be able to render the list at all.
The text was updated successfully, but these errors were encountered:
The first statement means that the orderBy model for the filter would not be initalized, which does not mean the phones model (list). Maybe this should be clarified.
On step 4 (http://docs.angularjs.org/tutorial/step_04), the docs say this about what would happen if there were no default order in the controller:
"If we had not set the default value here, the model would stay uninitialized until our user picks an option from the drop down menu."
But then you go down to the experiments section and it says this:
"In the PhoneListCtrl controller, remove the statement that sets the orderProp value and you'll see that Angular will temporarily add a new "unknown" option to the drop-down list and the ordering will default to unordered/natural order."
This contradicts the earlier statement. The experiment text is correct, but the first statement leads you to believe that Angular won't be able to render the list at all.
The text was updated successfully, but these errors were encountered: