| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Update docs to reflect that $http no longer requires passing in an HTTP method, as changed in #6401.
|
|
|
|
|
|
Closes #6709
|
|
On page http://docs.angularjs.org/tutorial/step_05 link is broken.
Should point to http://docs.angularjs.org/guide/services NOT http://docs.angularjs.org/guide/dev_guide.services
Closes #6714
|
|
The "runnableExample.template.html" template overrides the one in the
dgeni-packages "examples" package with a similar template that also has
a link to a special Plunker URL that can pull in the example from our
code.angularjs.org website.
|
|
|
|
Closes #6706
|
|
Fixed a minor error in link
Closes #6701
|
|
- step_05.ngdoc
- step_06.ngdoc
- step_07.ngdoc
- step_08.ngdoc
Closes #6686
Closes #6687
Closes #6688
Closes #6689
|
|
Closes #5012
|
|
|
|
This is to deal with https://github.com/npm/npm/issues/3581
See the previous commit for more info.
Closes #6672
|
|
from our experiements it appears that the presense or absense of the from and resolved properties
makes no difference on the behavior of but updates these properties
with different values depending on different state of the cache and node_modules.
So in order to get clean diffs during updates, we are just going to drop these properties and have
a script to do this automatically.
Long term this should be fixed in npm: https://github.com/npm/npm/issues/3581
|
|
|
|
|
|
|
|
This reverts commit d5294ebfa0e762d4a891a17869b7a14f99113d5a.
It turned out to be more work and I don't wanna deal with it right now.
|
|
|
|
Now the SHA can be short/long, whateva.
|
|
|
|
PR #5547 introduced conversion of all 0 status codes to 404 for cases
where no response was recieved (previously this was done for the
file:// protocol only). But this mechanism is too eager and
masks legitimate cases where status 0 should be returned. This commits
reverts to the previous mechanism of handling 0 status code for the
file:// protocol (converting 0 to 404) while retaining the returned
status code 0 for all the protocols other than file://
Fixes #6074
Fixes #6155
|
|
|
|
|
|
|
|
Closes #6654
|
|
Closes #6539
|
|
|
|
|
|
|
|
|
|
|
|
The recent $$RAFProvider which is a wrapper for the native
requestAnimationFrame method doesn't use the mozRequestAnimationFrame.
Old versions of FF (20 for example) crash if ngAnimate is included
No breaking changes and fix issue https://github.com/angular/angular.js/issues/6535
Closes #6535
Closes #6540
|
|
Related to #6630
|
|
|
|
This will make the following commit clearer when the update is run.
|
|
|
|
|
|
We need to be able to build angular at older shas, without the lock file / shrinkwrap file
the dependencies will resolve differently on different machines and at different times.
This will help us avoid broken builds and hard to track down issues.
I had to manually edit this file after it was generated because `npm shrinkwrap` will install
optional dependencies as if they were hard dependencies.
See: https://github.com/npm/npm/issues/2679#issuecomment-37361236
My manual edit:
```
diff --git a/npm-shrinkwrap.json b/npm-shrinkwrap.json
index 756df44..dc157eb 100644
--- a/npm-shrinkwrap.json
+++ b/npm-shrinkwrap.json
@@ -3110,19 +3110,7 @@
"chokidar": {
"version": "0.8.1",
"from": "https://registry.npmjs.org/chokidar/-/chokidar-0.8.1.tgz",
- "resolved": "https://registry.npmjs.org/chokidar/-/chokidar-0.8.1.tgz",
- "dependencies": {
- "fsevents": {
- "version": "0.1.6",
- "from": "fsevents@0.1.6",
- "resolved": "https://registry.npmjs.org/fsevents/-/fsevents-0.1.6.tgz"
- },
- "recursive-readdir": {
- "version": "0.0.2",
- "from": "recursive-readdir@0.0.2",
- "resolved": "https://registry.npmjs.org/recursive-readdir/-/recursive-readdir-0.0.2.tgz"
- }
- }
+ "resolved": "https://registry.npmjs.org/chokidar/-/chokidar-0.8.1.tgz"
},
"glob": {
"version": "3.2.9",
```
Additionally chokidar doesn't list the dependencies above as optional, but that will hopefully
be soon fixed: https://github.com/paulmillr/chokidar/pull/106
In the meantime the patch from the PR above needs to be applied to
node_modules/karma/node_modules/chokidar/package.json before running `npm shrinkwrap`
----
After this change is applied, angular core developers don't need to do anything differently,
except when updating dependencies we need to call `npm update && npm shrinkwrap --dev`
followed by reappling my patch above until npm's bug.
Closes #6653
|
|
|
|
The new version of dgeni-packages/ngdoc generates a manifest for each
example that can be used by plunker.
|
|
In relation to https://github.com/angular/dgeni-packages/pull/8
Closes #6641
|
|
|
|
The docs were relying on the grunt/util module for getting version info
but this was unreliable and full of custom regexes. This is moved into
a new version-info module that makes much better use of the semver library.
|
|
|
|
Moving to new lines & making it bold to avoid confusion
when they r all in same line without any separation
Closes #6633
|
|
Closes #6631
|
|
change $route.routes property type to Object, property is marked incorrectly as an Array
Closes #6552
|
|
the controller reference was breaking the custom validation example
Closes #6525
Closes #6533
|
