From 33e1bdc543bcb7875dcc004d487333393670ed2d Mon Sep 17 00:00:00 2001
From: Peter Bacon Darwin
Date: Sun, 16 Feb 2014 22:02:31 +0000
Subject: chore(errors): rename folders to match namespaces

---
 docs/content/error/$resource/badargs.ngdoc   |  9 +++++++++
 docs/content/error/$resource/badcfg.ngdoc    | 11 +++++++++++
 docs/content/error/$resource/badmember.ngdoc | 27 +++++++++++++++++++++++++++
 docs/content/error/$resource/badname.ngdoc   |  8 ++++++++
 4 files changed, 55 insertions(+)
 create mode 100644 docs/content/error/$resource/badargs.ngdoc
 create mode 100644 docs/content/error/$resource/badcfg.ngdoc
 create mode 100644 docs/content/error/$resource/badmember.ngdoc
 create mode 100644 docs/content/error/$resource/badname.ngdoc

(limited to 'docs/content/error/$resource')

diff --git a/docs/content/error/$resource/badargs.ngdoc b/docs/content/error/$resource/badargs.ngdoc
new file mode 100644
index 00000000..834c7826
--- /dev/null
+++ b/docs/content/error/$resource/badargs.ngdoc
@@ -0,0 +1,9 @@
+@ngdoc error
+@name $resource:badargs
+@fullName Too Many Arguments
+@description
+
+This error occurs when specifying too many arguments to a {@link ngResource.$resource `$resource`} action, such as `get`, `query` or any user-defined custom action.
+These actions may take up to 4 arguments.
+
+For more information, refer to the {@link ngResource.$resource `$resource`} API reference documentation.
diff --git a/docs/content/error/$resource/badcfg.ngdoc b/docs/content/error/$resource/badcfg.ngdoc
new file mode 100644
index 00000000..87e1ed26
--- /dev/null
+++ b/docs/content/error/$resource/badcfg.ngdoc
@@ -0,0 +1,11 @@
+@ngdoc error
+@name $resource:badcfg
+@fullName Response does not match configured parameter
+@description
+
+This error occurs when the {@link ngResource.$resource `$resource`} service expects a response that can be deserialized as an array, receives an object, or vice versa.
+By default, all resource actions expect objects, except `query` which expects arrays.
+
+To resolve this error, make sure your `$resource` configuration matches the actual format of the data returned from the server.
+
+For more information, see the {@link ngResource.$resource `$resource`} API reference documentation.
diff --git a/docs/content/error/$resource/badmember.ngdoc b/docs/content/error/$resource/badmember.ngdoc
new file mode 100644
index 00000000..4a61eb9b
--- /dev/null
+++ b/docs/content/error/$resource/badmember.ngdoc
@@ -0,0 +1,27 @@
+@ngdoc error
+@name $resource:badmember
+@fullName Syntax error in param value using @member lookup
+@description
+
+Occurs when there is a syntax error when attempting to extract a param
+value from the data object.
+
+Here's an example of valid syntax for `params` or `paramsDefault`:
+
+````javascript
+{
+  bar: '@foo.bar'
+}
+````
+
+The part following the `@`, `foo.bar` in this case, should be a simple
+dotted member lookup using only ASCII identifiers.  This error occurs
+when there is an error in that expression.  The following are all syntax
+errors
+
+ | Value   | Error          |
+ |---------|----------------|
+ | `@`     | Empty expression following `@`. |
+ | `@1.a`  | `1` is an invalid javascript identifier. |
+ | `@.a`   | Leading `.` is invalid. |
+ | `@a[1]` | Only dotted lookups are supported (no index operator) |
diff --git a/docs/content/error/$resource/badname.ngdoc b/docs/content/error/$resource/badname.ngdoc
new file mode 100644
index 00000000..99f73bdc
--- /dev/null
+++ b/docs/content/error/$resource/badname.ngdoc
@@ -0,0 +1,8 @@
+@ngdoc error
+@name $resource:badname
+@fullName Cannot use hasOwnProperty as a parameter name
+@description
+
+Occurs when you try to use the name `hasOwnProperty` as a name of a parameter.
+Generally, a name cannot be `hasOwnProperty` because it is used, internally, on a object
+and allowing such a name would break lookups on this object.
\ No newline at end of file
-- 
cgit v1.2.3