Client config file #574
janaakhterov
started this conversation in
Ideas
Replies: 2 comments 1 reply
-
|
It might be easier to just add/modify fields in the config. On the other hand it might be easier for developers to use/understand a type where comments can be added. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Is it currently possible to specify a network name for a custom network in config file? I think it currently is not. That's something that needs to be added. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The current config for client looks something like
{ "operator": { "accountId": "<id>", "privateKey": "<key>" }, "network": "testnet", "mirrorNetwork": "testnet" }However,
Clienthas so many other configuration options that are not included here, and the list grows frequently.maxTransactionFeemaxQueryPaymentsignOnDemandrequestTimeoutcloseDurationmaxAttemptsnodeWaitTimemaxNodeAttemptsmaxNodesPerTransactionWhat I propose is two things:
{ "operator": { "accountId": "<id>", "privateKey": "<key>" }, "network": "testnet", "mirrorNetwork": "testnet", "maxTransactionFee": "2 ℏ", "maxQueryPayment": "2 ℏ" }Configwhich contains all these fields, and updateClientto pass-through the setters and getters and/or implementClient.getConfig()which returns theConfigallowing the user to easily modify it.Beta Was this translation helpful? Give feedback.
All reactions