lbrycrd/doc/release-notes-16185.md

RPC changes
-----------
The `gettransaction` RPC now accepts a third (boolean) argument `verbose`. If
set to `true`, a new `decoded` field will be added to the response containing
the decoded transaction. This field is equivalent to RPC `decoderawtransaction`,
or RPC `getrawtransaction` when `verbose` is passed.
doc: Add release note for the new gettransaction argument 2019-06-13 00:30:15 +02:00			`RPC changes`
			`-----------`
rpc: fix regression in gettransaction PR 16866 renamed the 'decode' argument in gettransaction to 'verbose' to make it more consistent with other RPC calls like getrawtransaction. However, it seems it inadvertently overloaded the 'details' fields when 'verbose' is passed. The result is that the original 'details' fields are no longer returned, which seems to be a breaking API change. This PR takes the simplest path to restoring the 'details' fields by renaming them from 'details' back to 'decoded', while leaving the 'verbose' argument for API consistency. It also addresses [this comment](https://github.com/bitcoin/bitcoin/pull/16185#discussion_r320740413) to mention that the 'decoded' field is identical to decoderawtransaction. Update the RPC help, functional test, and release note. 2019-09-14 19:48:38 +02:00			The `gettransaction` RPC now accepts a third (boolean) argument `verbose`. If
			set to `true`, a new `decoded` field will be added to the response containing
			the decoded transaction. This field is equivalent to RPC `decoderawtransaction`,
			or RPC `getrawtransaction` when `verbose` is passed.