Uh oh!
There was an error while loading. Please reload this page.
refactor: currency types - #1238
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
| nodeConnectionConfig?: Partial<NodeConnectionConfig>; | ||
| signatureProvider?: SignatureProviderTypes.ISignatureProvider; | ||
| useMockStorage?: boolean; | ||
| currencies?: CurrencyInput[]; |
There was a problem hiding this comment.
Breaking: I suggest to remove this parameter as it's redundant with currencyManager
There was a problem hiding this comment.
Agreed it's redundant, but is the currencyManager the better choice? I'm not super familiar.
There was a problem hiding this comment.
between the two? I would say yes: it enables injecting your own implementation, and the CurrencyManager contains more than just a list of currencies. For instance, it contains the list of Aggregators for conversion
There was a problem hiding this comment.
Okay. 👍 Thanks for explaining
c33e957 to
0def2baCompared68636a to
8e03773CompareApply suggestions from code review
060bdc0 to
c165abaCompare
Move all types to the
typespackage for better consistency with other types and as a first step to reduce unnecessary dependencies to the currency package.BREAKING: types must be updated with
CurrencyTypesprefix, imported from@requestnetwork/typespackage.BREAKING: the
currenciesfield has been removed from theRequestNetworkclient parameters. UsecurrencyManager: new CurrencyManager(CURRENCIES)instead.