Closed rockacola closed 4 years ago
I think it makes sense to use the explicit one since the network object is a direct pass-through to neon-js. We could consider aliasing NetworkItem => neonCore.rpc.Network to support future differentiation?
Roll the consideration forward to future release.
Won't do, consider explicit interface out-weights benefits of combining with neonCore.rpc.Network
, especially for short term future.
[discussion ticket]
Consideration for removing custom defined
NetworkItem
interface, as it is a dumbed down version ofneonCore.rpc.Network
interface.Pro:
Con:
neonCore.rpc.Network
interface definition can be a tricker to understand