mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-11-27 15:15:50 +00:00
find/replace all universal error types links
This commit is contained in:
@@ -96,5 +96,5 @@ The response follows the [standard format](#response-formatting), with a success
|
||||
|
||||
### Possible Errors
|
||||
|
||||
* Any of the [universal error types](#universal-errors).
|
||||
* Any of the [universal error types][].
|
||||
* `badSeed` - The request provided an invalid seed value. This usually means that the seed value appears to be a valid string of a different format, such as an account address or validation public key.
|
||||
|
||||
@@ -187,6 +187,6 @@ For more information about multi-signing and signer lists, see [Multi-Signing](r
|
||||
|
||||
### Possible Errors
|
||||
|
||||
* Any of the [universal error types](#universal-errors).
|
||||
* Any of the [universal error types][].
|
||||
* `invalidParams` - One or more fields are specified incorrectly.
|
||||
* `badSeed` - The request specified a disallowed seed value (in the `passphrase`, `seed`, or `seed_hex` fields), such as an empty string, or a string resembling a XRP Ledger address.
|
||||
|
||||
@@ -62,7 +62,7 @@ Use this command with no parameter to query the existing `can_delete` setting.
|
||||
|
||||
### Possible Errors
|
||||
|
||||
* Any of the [universal error types](#universal-errors).
|
||||
* Any of the [universal error types][].
|
||||
* `notEnabled` - Not enabled in configuration.
|
||||
* `notReady` - Not ready to handle this request.
|
||||
* `lgrNotFound` - Ledger not found.
|
||||
|
||||
@@ -64,5 +64,5 @@ The response follows the [standard format](#response-formatting), with a success
|
||||
|
||||
### Possible Errors
|
||||
|
||||
* Any of the [universal error types](#universal-errors).
|
||||
* Any of the [universal error types][].
|
||||
* `internal` if one the parameters is specified incorrectly. (This is a bug; the intended error code is `invalidParams`.)
|
||||
|
||||
@@ -173,6 +173,6 @@ When the server is in the progress of fetching a ledger, but has not yet finishe
|
||||
|
||||
### Possible Errors
|
||||
|
||||
* Any of the [universal error types](#universal-errors).
|
||||
* Any of the [universal error types][].
|
||||
* `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing. This error can also occur if you specify a ledger index equal or higher than the current in-progress ledger.
|
||||
* `lgrNotFound` - If the ledger is not yet available. This indicates that the server has started fetching the ledger, although it may fail if none of its connected peers have the requested ledger. (Previously, this error used the code `ledgerNotFound` instead.) [Updated in: rippled 0.30.1][New in: rippled 0.30.1]
|
||||
|
||||
@@ -131,5 +131,5 @@ Otherwise, the request contains the following field:
|
||||
|
||||
### Possible Errors
|
||||
|
||||
* Any of the [universal error types](#universal-errors).
|
||||
* Any of the [universal error types][].
|
||||
* `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
|
||||
|
||||
@@ -72,4 +72,4 @@ The response follows the [standard format](#response-formatting), with a success
|
||||
|
||||
### Possible Errors
|
||||
|
||||
* Any of the [universal error types](#universal-errors).
|
||||
* Any of the [universal error types][].
|
||||
|
||||
@@ -91,6 +91,6 @@ The response follows the [standard format](#response-formatting), with a success
|
||||
|
||||
### Possible Errors
|
||||
|
||||
* Any of the [universal error types](#universal-errors).
|
||||
* Any of the [universal error types][].
|
||||
* `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
|
||||
* Cannot connect in standalone mode - Network-related commands are disabled in stand-alone mode.
|
||||
|
||||
@@ -55,5 +55,5 @@ The response follows the [standard format](#response-formatting), with a success
|
||||
|
||||
### Possible Errors
|
||||
|
||||
* Any of the [universal error types](#universal-errors).
|
||||
* Any of the [universal error types][].
|
||||
* `notStandAlone` - If the `rippled` server is not currently running in stand-alone mode.
|
||||
|
||||
@@ -80,4 +80,4 @@ The response follows the [standard format](#response-formatting), with a success
|
||||
|
||||
### Possible Errors
|
||||
|
||||
* Any of the [universal error types](#universal-errors).
|
||||
* Any of the [universal error types][].
|
||||
|
||||
@@ -82,5 +82,5 @@ The response follows the [standard format](#response-formatting), with a success
|
||||
|
||||
### Possible Errors
|
||||
|
||||
* Any of the [universal error types](#universal-errors).
|
||||
* Any of the [universal error types][].
|
||||
* `badSeed` - The request provided an invalid secret value. This usually means that the secret value appears to be a valid string of a different format, such as an account address or validation public key.
|
||||
|
||||
@@ -225,4 +225,4 @@ The results of the `consensus_info` command can vary dramatically if you run it
|
||||
|
||||
### Possible Errors
|
||||
|
||||
* Any of the [universal error types](#universal-errors).
|
||||
* Any of the [universal error types][].
|
||||
|
||||
@@ -184,5 +184,5 @@ The response follows the [standard format](#response-formatting), with a success
|
||||
|
||||
### Possible Errors
|
||||
|
||||
* Any of the [universal error types](#universal-errors).
|
||||
* Any of the [universal error types][].
|
||||
* `badFeature` - The `feature` specified was invalidly formatted, or the server does not know an amendment with that name.
|
||||
|
||||
@@ -153,4 +153,4 @@ The fields describing a fetch in progress are subject to change without notice.
|
||||
|
||||
### Possible Errors
|
||||
|
||||
* Any of the [universal error types](#universal-errors).
|
||||
* Any of the [universal error types][].
|
||||
|
||||
@@ -144,5 +144,5 @@ For most other entries, the value indicates the number of objects of that type c
|
||||
|
||||
### Possible Errors
|
||||
|
||||
* Any of the [universal error types](#universal-errors).
|
||||
* Any of the [universal error types][].
|
||||
* `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
|
||||
|
||||
@@ -406,4 +406,4 @@ Each member of the `peers` array is a peer object with the following fields:
|
||||
|
||||
### Possible Errors
|
||||
|
||||
* Any of the [universal error types](#universal-errors).
|
||||
* Any of the [universal error types][].
|
||||
|
||||
@@ -228,4 +228,4 @@ The response follows the [standard format](#response-formatting). Additional fie
|
||||
|
||||
### Possible Errors
|
||||
|
||||
* Any of the [universal error types](#universal-errors).
|
||||
* Any of the [universal error types][].
|
||||
|
||||
@@ -126,4 +126,4 @@ Each member of the `validator_sites` field array is an object with the following
|
||||
|
||||
### Possible Errors
|
||||
|
||||
* Any of the [universal error types](#universal-errors).
|
||||
* Any of the [universal error types][].
|
||||
|
||||
@@ -174,4 +174,4 @@ Each member of the `publisher_lists` array is an object with the following field
|
||||
|
||||
### Possible Errors
|
||||
|
||||
* Any of the [universal error types](#universal-errors).
|
||||
* Any of the [universal error types][].
|
||||
|
||||
Reference in New Issue
Block a user