Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request includes several changes to the
nodebalancer
. The most important changes include updating the JSON structure in the README, modifying thebalances.go
andconfigs.go
files to include additional chain information, and updating thecontracts.json
structure.Documentation Updates:
nodebalancer/README.md
: Updated the JSON structure to include additional chain information such aschain_id
,name
, andimage_url
. The top-level keys are now chain IDs, and thebalances
are nested within each chain object. [1] [2]Codebase Enhancements:
nodebalancer/cmd/nodebalancer/balances.go
: Introduced a newChainInfo
struct to encapsulate chain-related information and updated theBalancesResponse
type to useChainInfo
instead ofChainBalances
.nodebalancer/cmd/nodebalancer/balances.go
: Modified thegetBalances
function to populate theBalancesResponse
withChainInfo
objects, includingchain_id
,name
, andimage_url
.nodebalancer/cmd/nodebalancer/configs.go
: Added new fields to theChainConfig
struct forchain_id
,name
, andimage_url
.These changes improve the readability and usability of the JSON responses and configuration files by including more detailed information about each blockchain.
response example.