angular.js/src/ngResource, branch g3_v1_3

angular.js/src/ngResource, branch g3_v1_3 docs($resource): fix example using promise 2014-03-13T23:33:38+00:00 Wesley Cho 2014-01-28T03:59:10+00:00 91ef3a31a0080de2b5a3db8f2a20dba00dcd2ae1

docs(*): ensure jsdoc type expressions are valid 2014-03-02T15:02:29+00:00 Peter Bacon Darwin 2014-02-27T21:54:26+00:00 e89139dc9dd4a9c104d71167bea4987b766767df

docs(modules): remove unused {@installModule} tags 2014-02-19T21:22:27+00:00 Peter Bacon Darwin 2014-02-19T21:22:27+00:00 cc1f7539d414038212b83dca86cf04f71731f24b

style: remove ws and enfore no-trailing-ws jscs rule 2014-02-18T18:44:48+00:00 Igor Minar 2014-02-18T11:04:42+00:00 481508d0e7ae9e4984ea380b9a43e589551c7a5b

docs(api): escape params that have <object> in their type 2014-02-16T19:03:44+00:00 Peter Bacon Darwin 2014-02-14T15:52:17+00:00 2123772a653eeb969ef6f8c21d1daee878098fe1 Really the doc-gen process should escape there but for now this should stop the layout from breaking.

Really the doc-gen process should escape there but for now this should
stop the layout from breaking.

docs(ngResource): fix over-length line 2014-02-16T19:03:41+00:00 Peter Bacon Darwin 2014-02-07T20:58:56+00:00 9f828a07dc63ed13bda991cc7cf21cae89b64948

docs(bike-shed-migration): let markdown deal with extenal links 2014-02-16T19:03:41+00:00 Peter Bacon Darwin 2014-02-07T20:40:35+00:00 2f7c57233ad2d578952dbba5c63ae8d50c1b487a It is problematic to use {@link} tags with external links because the markdown parser converts them to links for us before we parse the @links. This means that the following tag: ``` {@link http://www.google.com Google} ``` get converted to: ``` {@link <a href="http://www.google.com/"></a> Google} ``` Our {@link} parser then converts this to: ``` <a href="<a"><</a>href="http://www.google.com/"></a> Google} ``` which is clearly a mess. The best solution is not to use {@link} tags for external links and just use the standard markdown syntax: ``` [Google](http://www.google.com) ``` In the long run, we could look into configuring or modifying `marked` not to convert these external links or we could provide a "pre-parser" processor that dealt with such links before `marked` gets its hands on it.

It is problematic to use {@link} tags with external links because the
markdown parser converts them to links for us before we parse the @links.
This means that the following tag:

```
{@link http://www.google.com Google}
```

get converted to:

```
{@link <a href="http://www.google.com/"></a> Google}
```

Our {@link} parser then converts this to:

```
<a href="<a">&lt;</a>href="http://www.google.com/"></a> Google}
```

which is clearly a mess.  The best solution is not to use {@link} tags
for external links and just use the standard markdown syntax:

```
[Google](http://www.google.com)
```

In the long run, we could look into configuring or modifying `marked` not
to convert these external links or we could provide a "pre-parser"
processor that dealt with such links before `marked` gets its hands on it.

docs(all): convert <pre>/</pre> snippets to GFM snippets 2014-02-16T19:03:40+00:00 Caitlin Potter 2014-02-06T14:02:18+00:00 f7d28cd377f06224247b950680517a187a7b6749

docs(bike-shed-migration): convert doctype and names 2014-02-16T19:03:40+00:00 Peter Bacon Darwin 2014-02-06T13:33:42+00:00 2e641ac49f121a6e2cc70bd3879930b44a8a7710

fix(ngResource): don't filter "$"-prefixed properties from ngResource requests/responses 2014-02-04T15:51:24+00:00 Thomas Belin 2014-01-07T15:09:37+00:00 d2e4e499862aeca157dbe7a7422c465e7c79205e ngResource no longer filters properties prefixed with a single "$" character from requests or responses, correcting a regression introduced in 1.2.6 (cb29632a) which caused shallowCopy and shallowClearAndCopy to ignore properties prefixed with a single "$". Closes #5666 Closes #6080 Closes #6033

ngResource no longer filters properties prefixed with a single "$" character from requests or
responses, correcting a regression introduced in 1.2.6 (cb29632a) which caused shallowCopy and
shallowClearAndCopy to ignore properties prefixed with a single "$".

Closes #5666
Closes #6080
Closes #6033