Chain & Assets Display Priorities

[svojsu]

SUMMARY

The PR introduces chains v23, enabling support for syncing display priorities for chains and assets.

SOLUTION

The chains.json file now contains a top-level object consisting of three fields:

• assetDisplayPriorities – a map of priority values indexed by asset symbol
• chainDisplayPriorities – a map of priority values indexed by chainId
• chains – an array of chain objects (unchanged from the previous structure)

Clients should incorporate assetDisplayPriorities and chainDisplayPriorities into their chain syncing logic. Domain model objects created on the client side should include a displayPriority field, which is populated during the conversion from the chains.json response to the client's domain model objects.

iOS example of this mapping:

let newChainModel = ChainModel(
        remoteModel: remoteModel,
        assets: Set(newAssets),
        nodes: Set(orderedNodes),
        syncMode: syncMode,
        order: additionals.order,
        connectionMode: localModel?.connectionMode ?? .autoBalanced,
        displayPriority: chainPriorities[remoteModel.chainId]
)

SCREEN RECORDINGS

sorting_demo.mov

[github-actions]

🧪 Test results
https://github.com/novasamatech/nova-utils/actions/runs/20128433429/attempts/1#summary-57763596393