[js] Rewrite the error module to export specific types for each error…

… code Only the error codes used by the W3C spec are supported on the class definitions (and we still provide a means to translate number to error type)
SeleniumHQ · Nov 18, 2015 · c3eccba · c3eccba
1 parent f862c22
commit c3eccba
Show file tree

Hide file tree

Showing 5 changed files with 650 additions and 7 deletions.
diff --git a/javascript/node/selenium-webdriver/CHANGES.md b/javascript/node/selenium-webdriver/CHANGES.md
@@ -4,6 +4,11 @@
     `promise.Promise#thenCatch()` is not yet deprecated, but it simply
     delegates to `catch`.
 * Changed some `io` operations to use native promises.
+* Rewrote the `error` module to export an Error subtype for each type of error
+    defined in the [W3C WebDriver spec](https://w3c.github.io/webdriver/webdriver-spec.html#handling-errors).
+    For the export types, the `code` property is now the string code used by
+    the W3C spec and _not_ the numeric code used by the Selenium project's
+    wire protocol.
 
 ## v2.48.2