Erc 7540 rid updates #11
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
ci.yml
on: pull_request
Save PR Number
5s
HTMLProofer
7m 12s
Link Check
13s
CodeSpell
12s
EIP Walidator
7s
Markdown Linter
6s
Annotations
11 errors
Markdown Linter
Process completed with exit code 1.
|
Markdown Linter
Unable to process file command 'env' successfully.
|
Markdown Linter
Invalid value. Matching delimiter not found 'EOF'
|
proposals must be referenced with the form `ERC-N` (not `ERCN` or `ERC N`):
ERCS/erc-7540.md#L101
error[markdown-re-erc-dash]: proposals must be referenced with the form `ERC-N` (not `ERCN` or `ERC N`)
--> ERCS/erc-7540.md
|
101 | If the length of `data` is not 0, the Request MUST send an `onERC7540DepositReceived` callback to `receiver` following the interface of ERC7540DepositReceiver described in "Request Callbacks" section. If the length of `data` is 0, the Request MUST NOT send a callback.
|
= info: the pattern in question: `(?i)erc[\s]*[0-9]+`
= help: see https://ethereum.github.io/eipw/markdown-re-erc-dash/
|
proposals must be referenced with the form `ERC-N` (not `ERCN` or `ERC N`):
ERCS/erc-7540.md#L196
error[markdown-re-erc-dash]: proposals must be referenced with the form `ERC-N` (not `ERCN` or `ERC N`)
--> ERCS/erc-7540.md
|
196 | If the length of `data` is not 0, the Request MUST send an `onERC7540RedeemReceived` callback to `receiver` following the interface of ERC7540RedeemReceiver described in "Request Callbacks" section. If the length of `data` is 0, the Request MUST NOT send a callback.
|
= info: the pattern in question: `(?i)erc[\s]*[0-9]+`
|
proposals must be referenced with the form `ERC-N` (not `ERCN` or `ERC N`):
ERCS/erc-7540.md#L336
error[markdown-re-erc-dash]: proposals must be referenced with the form `ERC-N` (not `ERCN` or `ERC N`)
--> ERCS/erc-7540.md
|
336 | #### ERC7540DepositReceiver
|
= info: the pattern in question: `(?i)erc[\s]*[0-9]+`
|
proposals must be referenced with the form `ERC-N` (not `ERCN` or `ERC N`):
ERCS/erc-7540.md#L362
error[markdown-re-erc-dash]: proposals must be referenced with the form `ERC-N` (not `ERCN` or `ERC N`)
--> ERCS/erc-7540.md
|
362 | #### ERC7540RedeemReceiver
|
= info: the pattern in question: `(?i)erc[\s]*[0-9]+`
|
proposals must be referenced with the form `ERC-N` (not `ERCN` or `ERC N`):
ERCS/erc-7540.md#L395
error[markdown-re-erc-dash]: proposals must be referenced with the form `ERC-N` (not `ERCN` or `ERC N`)
--> ERCS/erc-7540.md
|
395 | ERC7540DepositReceiver contracts MUST return the constant value `true` if TODO is passed through the `interfaceID` argument.
|
= info: the pattern in question: `(?i)erc[\s]*[0-9]+`
|
proposals must be referenced with the form `ERC-N` (not `ERCN` or `ERC N`):
ERCS/erc-7540.md#L397
error[markdown-re-erc-dash]: proposals must be referenced with the form `ERC-N` (not `ERCN` or `ERC N`)
--> ERCS/erc-7540.md
|
397 | ERC7540RedeemReceiver contracts MUST return the constant value `true` if TODO is passed through the `interfaceID` argument.
|
= info: the pattern in question: `(?i)erc[\s]*[0-9]+`
|
proposals must be referenced with the form `ERC-N` (not `ERCN` or `ERC N`):
ERCS/erc-7540.md#L406
error[markdown-re-erc-dash]: proposals must be referenced with the form `ERC-N` (not `ERCN` or `ERC N`)
--> ERCS/erc-7540.md
|
406 | Certain Vaults especially `rid==0` cases benefit from using the underlying ERC4626 methods for claiming because there is no discrimination at the `rid` level. This standard is written primarily with those use cases in mind. A future standard can optimize for nonzero RID with support for claiming and transferring requests discriminated also with an `rid`.
|
= info: the pattern in question: `(?i)erc[\s]*[0-9]+`
|
EIP Walidator
validation found errors :(
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
pr_number
Expired
|
84 Bytes |
|