Error: [ethjs-rpc] rpc error with payload

[homer1384]

ethjs-rpc

Before opening a new issue, please take a moment to review our community guidelines to make the contribution process easy and effective for everyone involved.

Before opening a new issue, you may find an answer in already closed issues:
https://github.com/ethjs/ethjs-rpc/issues?q=is%3Aissue+is%3Aclosed

Issue Type

• Bug (https://github.com/ethjs/ethjs-rpc/blob/master/.github/CONTRIBUTING.md#bug-reports)
• Feature (https://github.com/ethjs/ethjs-rpc/blob/master/.github/CONTRIBUTING.md#feature-requests)

Description

(Add images if possible)

Steps to reproduce

(Add link to a demo on https://jsfiddle.net or similar if possible)

Versions

• Node/NPM:
• Browser:

[SilentCicero]

Can you further expand on your issue?

…

Sent from my iPhone

On Dec 6, 2017, at 5:24 AM, homer1384 ***@***.***> wrote: ethjs-rpc Before opening a new issue, please take a moment to review our community guidelines to make the contribution process easy and effective for everyone involved. Before opening a new issue, you may find an answer in already closed issues: https://github.com/ethjs/ethjs-rpc/issues?q=is%3Aissue+is%3Aclosed Issue Type Bug (https://github.com/ethjs/ethjs-rpc/blob/master/.github/CONTRIBUTING.md#bug-reports) Feature (https://github.com/ethjs/ethjs-rpc/blob/master/.github/CONTRIBUTING.md#feature-requests) Description (Add images if possible) Steps to reproduce (Add link to a demo on https://jsfiddle.net or similar if possible) Versions Node/NPM: Browser: — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[sulliwane]

I believe he meant could it be possible to get a better error object? (if not, then I will open an issue for that).

Currently, the error is a concat of many strings / stack trace...which is very unusable.

At least, It would be great to be able to access the:

• error code
• rpc error message

without having to parse the error string...

Thanks a lot !

[SilentCicero]

Yes, we totally could do this! Can you propose a PR? The codebase is very simple.

…

Sent from my iPhone

On May 18, 2018, at 11:57 AM, Victor ***@***.***> wrote: I believe he meant could it be possible to get a better error object? (if not, then I will open an issue for that). Currently, the error is a concat of many strings / stack trace...which is very unusable. At least, It would be great to be able to access the: error code rpc error message without having to parse the error string... Thanks a lot ! — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.