mirror of
https://github.com/bitcoin/bitcoin.git
synced 2024-11-19 09:53:47 +01:00
doc: update developer notes wrt unix epoch time
This commit is contained in:
parent
e2f32cb5c5
commit
d94d34f05f
@ -1014,7 +1014,7 @@ A few guidelines for introducing and reviewing new RPC interfaces:
|
||||
- A RPC method must either be a wallet method or a non-wallet method. Do not
|
||||
introduce new methods that differ in behavior based on the presence of a wallet.
|
||||
|
||||
- *Rationale*: as well as complicating the implementation and interfering
|
||||
- *Rationale*: As well as complicating the implementation and interfering
|
||||
with the introduction of multi-wallet, wallet and non-wallet code should be
|
||||
separated to avoid introducing circular dependencies between code units.
|
||||
|
||||
@ -1041,8 +1041,13 @@ A few guidelines for introducing and reviewing new RPC interfaces:
|
||||
|
||||
- *Rationale*: RPC methods registered with the same function pointer will be
|
||||
considered aliases and only the first method name will show up in the
|
||||
`help` rpc command list.
|
||||
`help` RPC command list.
|
||||
|
||||
- *Exception*: Using RPC method aliases may be appropriate in cases where a
|
||||
new RPC is replacing a deprecated RPC, to avoid both RPCs confusingly
|
||||
showing up in the command list.
|
||||
|
||||
- Use the `UNIX_EPOCH_TIME` constant when describing UNIX epoch time or
|
||||
timestamps in the documentation.
|
||||
|
||||
- *Rationale*: User-facing consistency.
|
||||
|
Loading…
Reference in New Issue
Block a user