Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: user friendly error on asset parse failure #4229

Merged
merged 1 commit into from Nov 10, 2023

Conversation

dandanlen
Copy link
Collaborator

Returns a clearer error if RpcAsset fails to parse.

@dandanlen dandanlen requested a review from a team as a code owner November 10, 2023 13:30
@dandanlen dandanlen requested review from jerryafr and acdibble and removed request for a team November 10, 2023 13:30
Copy link

codecov bot commented Nov 10, 2023

Codecov Report

Merging #4229 (8ee9a21) into main (f6981d6) will decrease coverage by 0%.
Report is 13 commits behind head on main.
The diff coverage is 100%.

@@          Coverage Diff           @@
##            main   #4229    +/-   ##
======================================
- Coverage     72%     72%    -0%     
======================================
  Files        383     384     +1     
  Lines      62348   62975   +627     
  Branches   62348   62975   +627     
======================================
+ Hits       44637   45031   +394     
- Misses     15376   15607   +231     
- Partials    2335    2337     +2     
Files Coverage Δ
state-chain/custom-rpc/src/lib.rs 25% <100%> (+1%) ⬆️

... and 56 files with indirect coverage changes

📣 Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today!

@martin-chainflip
Copy link
Contributor

nice

@dandanlen dandanlen merged commit 1de7247 into main Nov 10, 2023
41 checks passed
@dandanlen dandanlen deleted the feat/user-friendly-message-asset-parsing branch November 10, 2023 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants