chore(errors): rename folders to match namespaces

4 files changed, 0 insertions, 55 deletions

diff --git a/docs/content/error/resource/badargs.ngdoc b/docs/content/error/resource/badargs.ngdoc
deleted file mode 100644
index 834c7826..00000000
--- a/docs/content/error/resource/badargs.ngdoc
+++ /dev/null
@@ -1,9 +0,0 @@
-@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
deleted file mode 100644
index 87e1ed26..00000000
--- a/docs/content/error/resource/badcfg.ngdoc
+++ /dev/null
@@ -1,11 +0,0 @@
-@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
deleted file mode 100644
index 4a61eb9b..00000000
--- a/docs/content/error/resource/badmember.ngdoc
+++ /dev/null
@@ -1,27 +0,0 @@
-@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
deleted file mode 100644
index 99f73bdc..00000000
--- a/docs/content/error/resource/badname.ngdoc
+++ /dev/null
@@ -1,8 +0,0 @@
-@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