Update ERC-7683: Extending the standard #4932
Annotations
8 errors and 3 warnings
Run ethereum/eipw-action@be3fa642ec311d0b8e1fdb811e5c9b4ada3d3d93:
ERCS/erc-7683.md#L35
error[markdown-link-first]: the first match of the given pattern must be a link
--> ERCS/erc-7683.md
|
35 | - **User**: for the purposes of this document, the user is the end-user who is sending the ERC-7683 order.
|
= info: the pattern in question: `(?i)(?:eip|erc)-([0-9])+`
= help: see https://ethereum.github.io/eipw/markdown-link-first/
|
Run ethereum/eipw-action@be3fa642ec311d0b8e1fdb811e5c9b4ada3d3d93:
ERCS/erc-7683.md#L277
error[markdown-order-section]: body has extra section(s)
--> ERCS/erc-7683.md
|
277 | ## Examples
|
= help: see https://ethereum.github.io/eipw/markdown-order-section/
|
Run ethereum/eipw-action@be3fa642ec311d0b8e1fdb811e5c9b4ada3d3d93:
ERCS/erc-7683.md#L332
error[markdown-re-eip-dash]: proposals must be referenced with the form `EIP-N` (not `EIPN` or `EIP N`)
--> ERCS/erc-7683.md
|
332 | In this example, the Message sub-type allows the user to delegate destination chain contract execution to fillers. However, because...
|
= info: the pattern in question: `(?i)eip[\s]*[0-9]+`
= help: see https://ethereum.github.io/eipw/markdown-re-eip-dash/
|
Run ethereum/eipw-action@be3fa642ec311d0b8e1fdb811e5c9b4ada3d3d93:
ERCS/erc-7683.md#L332
error[markdown-re-erc-dash]: proposals must be referenced with the form `ERC-N` (not `ERCN` or `ERC N`)
--> ERCS/erc-7683.md
|
332 | In this example, the Message sub-type allows the user to delegate destination chain contract execution to fillers. However, because...
|
= info: the pattern in question: `(?i)erc[\s]*[0-9]+`
= help: see https://ethereum.github.io/eipw/markdown-re-erc-dash/
|
Run ethereum/eipw-action@be3fa642ec311d0b8e1fdb811e5c9b4ada3d3d93:
ERCS/erc-7683.md#L363
error[markdown-re-erc-dash]: proposals must be referenced with the form `ERC-N` (not `ERCN` or `ERC N`)
--> ERCS/erc-7683.md
|
363 | This design decision is motivated by the existence of many viable cross-chain messaging systems today offering settlement contracts...
|
= info: the pattern in question: `(?i)erc[\s]*[0-9]+`
|
Run ethereum/eipw-action@be3fa642ec311d0b8e1fdb811e5c9b4ada3d3d93:
ERCS/erc-7683.md#L332
error[markdown-rel-links]: non-relative link or image
--> ERCS/erc-7683.md
|
332 | In this example, the Message sub-type allows the user to delegate destination chain contract execution to fillers. However, because...
|
= help: see https://ethereum.github.io/eipw/markdown-rel-links/
|
Run ethereum/eipw-action@be3fa642ec311d0b8e1fdb811e5c9b4ada3d3d93:
ERCS/erc-7683.md#L332
error[markdown-rel-links]: non-relative link or image
--> ERCS/erc-7683.md
|
332 | In this example, the Message sub-type allows the user to delegate destination chain contract execution to fillers. However, because...
|
|
Run ethereum/eipw-action@be3fa642ec311d0b8e1fdb811e5c9b4ada3d3d93
validation found errors :(
|
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@47fbe2df0ad0e27efb67a70beac3555f192b062f. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Run ethereum/eipw-action@be3fa642ec311d0b8e1fdb811e5c9b4ada3d3d93:
ERCS/erc-7683.md#L365
warning[markdown-html-comments]: HTML comments are only allowed while `status` is one of: `Draft`, `Withdrawn`
--> ERCS/erc-7683.md
|
365 | <!-- TODO -->
|
= help: see https://ethereum.github.io/eipw/markdown-html-comments/
|
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "pr_number".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
Loading