| Age | Commit message (Collapse) | Author |
|
Before:
> Let's add some more logic to the example to
allow to enter and calculate the costs in different currencies and also pay the invoice.
After:
> Let's add some more logic to the example that
allows us to enter and calculate the costs in different currencies and also pay the invoice.
Closes #4903
|
|
|
|
Closes #4873
|
|
Remove reference to `employee` property as it's not used in the example.
Inject and use `$rootScope` applying `department` property as mentioned in text.
Closes #4839
|
|
The CSS styling in the ng-scope demo was using CSS classes (`.doc-example-live` and
`.show-scope') to prevent the styling for the demo from affecting the entire page.
Unfortunately elements containing these classes did not appear in JSFiddle or Plunker
when you click edit.
This fix moves the `.show-scope' class inside the demo (renaming it `.show-scope-demo`)
and removes the reliance on `.doc-example-live` altogether.
Closes #4838
|
|
Closes #4821
|
|
Correct " model property `spice` " to " model property `customSpice` " to match the code sample
Closes #4812
|
|
Closes #4793
|
|
Closes #4792
|
|
|
|
|
|
|
|
|
|
This refactors the filter guide docs into a single file.
Also removes out of date references to the fact that Angular used to enhance Arrays while evaluating expressions.
|
|
We have links to better videos now on the guide/index page. This one's time has past.
|
|
Before, there we multiple overview docs:
- guide/overview
- guide/introduction
- guide/dev_guide.mvc
- guide/dev_guide.mvc.understanding_model
- guide/dev_guide.mvc.understanding_view
- guide/concepts
Now we have:
- guide/introduction: High level description of Angular with the key benefits but without code or any concrete concepts
- guide/concepts: explains all important concepts with a simple example and contains deep links to the other parts of the guide.
All the old information was moved into existing documents or deleted when they were duplicates.
|
|
|
|
|
|
The example about transclusion and scopes worked only because the order of `scope` and `element`
arguments is wrong, which means that the `name' property of the scope is not really being updated.
To really work, the directive has to define its own scope, either a new child scope or, as is more
common with transclusion, an isolated scope.
Closes #4774
|
|
Closes #4748
|
|
Broken - $scope.spicy = 'very';
Works - $scope.spice = 'very';
Closes #4752
|
|
Inserted a couple of line breaks to increase readability.
Closes #4756
|
|
Closes #4714
|
|
Closes #4700
|
|
Add the word "to" to improve grammar.
Closes #4698
|
|
If you have zoomed into the page in your browser then the screen coordinate system no longer
matches the page coordinate system. To ensure that dragged elements work correctly when zoomed
we should use pageX/pageY rather than screenX/screenY.
Closes #4687
|
|
Nested bullet points don't appear very nicely so resorted to nested
heading for the Learning Resources and in particular Books sections.
Closes #4677
|
|
|
|
Closes #4674
|
|
Add note that `input()` fn matches ng-model instead of HTML name attribute.
About five users on forums were snagged by this assumption:
http://docs.angularjs.org/guide/dev_guide.e2e-testing#comment-898079915
Closes #4655
|
|
The escaping of the colon in the example CSS is incorrect.
Replace `ng\\:view {` with `ng\:view {`
Closes #4570
|
|
Closes #4601
|
|
Closes #4668
|
|
Closes #4667
|
|
Add a note to warn people starting new projects about Protractor replacing the
current ngScenario way of doing E2E testing.
Closes #4644
|
|
Closes #4647
|
|
Closes #4639
|
|
The BabyCtrl was a bit confusing and GrandChildCtrl seems to make more sense
with the whole "scope inheritance" concept.
Closes #4634
|
|
|
|
Closes #4615
|
|
Closes #4578
|
|
Change landing page to include a set of curated links with subject
headings as a guide through Angular's docs and other resources.
Closes #4470
|
|
The removed block is repeated from the unit-testing guide and appears
in an awkward place in this text.
Closes #4456
|
|
The example that demonstrates how to parse expressions can fail if you
pass in the same expression twice. By using "track by $index" we can
fix this.
Closes #4472
|
|
|
|
This also contains some whitespace corrections by my editor.
|
|
Closes #4405
|
|
Closes #4386
|
|
Remove mention of global controller functions
Convert larger examples to runnable demos
Remove mention of pre-1.0 controllers, in particular discussion of
controller inheritance.
TODO: Probably could do with updating to explain the "controller as" syntax
at some point.
Closes: #4373
|
|
Use the recommended `module.controller` syntax rather than global
functions to define controllers in the examples.
|