Dan Graham 7ffda66813 Fixed W3C error messaging (#182) ...

* Do proxying for W3C responses
  * If a W3C Response is provided by a proxy, map to the correct error
  * Checks if `value` is an object and `value.error` and maps it based on that (`value.error` is the W3C error code)
  * Broke off `errorFromCode` into `errorFromMJSONWPStatusCode` and `errorFromW3CJsonCode`
* Rename '.error' property to correct W3C property
  * The error property in the ProtocolError objects should match up with https://www.w3.org/TR/webdriver/#handling-errors under the 'JSON Error Code' column
  * Added tests for all of these
* Make ProxyRequestError work for W3C
  * Added an arg called `.w3c` that passes in the proxied W3C error
  * Fixed the `getActualError` function that looks for the .w3c variable and parses error from the code

2018-02-05 11:55:56 -08:00

..

basedriver

Rename 'mjsonwp' to 'protocol' (#178)

2018-01-29 12:41:14 -08:00

express

Rename 'mjsonwp' to 'protocol' (#178)

2018-01-29 12:41:14 -08:00

jsonwp-proxy

Fixed W3C error messaging (#182)

2018-02-05 11:55:56 -08:00

jsonwp-status

update readmes to make sense for new package

2016-05-06 08:42:29 -07:00

protocol

Fixed W3C error messaging (#182)

2018-02-05 11:55:56 -08:00