Which components does the task require to be changed? (think hard pls)
sncast
Description
We should allow saving the RPC URL so we don't have to use profiles for using this - we're not always in a project scope, and it seems excessive, if you only want to do a few transactions in a day.
We could also provide some free default options (set and forget) which would be configured in installation, if no config is detected on disk. Those can be re-configured later.
We should allow storing a few URLs and setting a default, which will be used if no other RPC ID was specified. This means we would have to store it in a file, in the installation directory, preserving it when migrating versions.
Missing RPC URL for commands that don't need it (mutlicall new/account import etc.) result in a confusing/frustrating experience where we HAVE to provide it no matter what. This should also be addressed by the solution of this
RPC URLs are poorly validated, this can be addressed in this or any other issue
RPC URL should not be a common flag, when introducing other offline-capable flags, we should be able to omit it
Arcticae
commented
2 weeks ago
Which components does the task require to be changed? (think hard pls)
sncast
Description
We should allow saving the RPC URL so we don't have to use profiles for using this - we're not always in a project scope, and it seems excessive, if you only want to do a few transactions in a day.
We could also provide some free default options (set and forget) which would be configured in installation, if no config is detected on disk. Those can be re-configured later.
We should allow storing a few URLs and setting a default, which will be used if no other RPC ID was specified. This means we would have to store it in a file, in the installation directory, preserving it when migrating versions.
Missing RPC URL for commands that don't need it (
mutlicall new/account importetc.) result in a confusing/frustrating experience where we HAVE to provide it no matter what. This should also be addressed by the solution of thisRPC URLs are poorly validated, this can be addressed in this or any other issue
RPC URL should not be a common flag, when introducing other offline-capable flags, we should be able to omit it