Operation error handling — tezblock Update #19
The easy digestible update summary for the current state and progress of the tezblock development with the goal to include the community as much as possible along the way.
Contract support & governance improvements were introduced in the last update. This update bring many new features and improvements, like better error handling for operations and more details for proposals.
Changes and improvements
Additional features and other small changes are in store with this update.
After feedback from the community and Baking Bad in a video, we have made improvements to the handling of failed operations. Errors are now displayed prominently on Transactions in human-readable form where already available, which will be extended in a next release.
Additionally across all tables on every page like the Originations Overview for failed operations the error description is displayed in a tooltip when hovering over the operation.
For Proposals more information has been added, a detailed description of the changes can be found for each proposal also links to the discussion taking place on Tezos Agora.
Improvements & changes
Additionally to the features many small changes have been done.
- Time has been invested in refactoring the whole code to support the ngrx approach.
- baker-table: is_baker refactoring
- baker-table: Tezos Nodes API update
- proposal-detail: period improvements
- contract-detail: transfer refactoring
Updates have been pushed to
The tezblock mainnet as well as the Babylonnet and Carthagenet deployment have been update.
👉 tezblock.io
👉 babylonnet.tezblock.io
👉 carthagenet.tezblock.io
As always we would like to hear your feedback. What features are the most important for you, have you found any issue? Please reach out to us on Telegram or Twitter.
