Skip to content

Update ERC-165: fix typo #6303

Update ERC-165: fix typo

Update ERC-165: fix typo #6303

Triggered via pull request February 23, 2025 05:39
Status Failure
Total duration 10m 54s
Artifacts 1

ci.yml

on: pull_request
Save PR Number
4s
Save PR Number
HTMLProofer
10m 28s
HTMLProofer
Link Check
13s
Link Check
CodeSpell
9s
CodeSpell
EIP Walidator
6s
EIP Walidator
Markdown Linter
7s
Markdown Linter
Fit to window
Zoom out
Zoom in

Annotations

13 errors and 1 warning
the first match of the given pattern must be a link: ERCS/erc-165.md#L22
error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-165.md | 22 | 3. How to detect if a contract implements ERC-165 | = info: the pattern in question: `(?i)(?:eip|erc)-([0-9])+` = help: see https://ethereum.github.io/eipw/markdown-link-first/
the first match of the given pattern must be a link: ERCS/erc-165.md#L57
error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-165.md | 57 | A contract that is compliant with ERC-165 shall implement the following interface (referred as `ERC165.sol`): | = info: the pattern in question: `(?i)(?:eip|erc)-([0-9])+`
the first match of the given pattern must be a link: ERCS/erc-165.md#L86
error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-165.md | 86 | ### How to Detect if a Contract Implements ERC-165 | = info: the pattern in question: `(?i)(?:eip|erc)-([0-9])+`
the first match of the given pattern must be a link: ERCS/erc-165.md#L89
error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-165.md | 89 | 2. If the call fails or return false, the destination contract does not implement ERC-165. | = info: the pattern in question: `(?i)(?:eip|erc)-([0-9])+`
the first match of the given pattern must be a link: ERCS/erc-165.md#L91
error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-165.md | 91 | 4. If the second call fails or returns false, the destination contract does not implement ERC-165. | = info: the pattern in question: `(?i)(?:eip|erc)-([0-9])+`
the first match of the given pattern must be a link: ERCS/erc-165.md#L92
error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-165.md | 92 | 5. Otherwise it implements ERC-165. | = info: the pattern in question: `(?i)(?:eip|erc)-([0-9])+`
the first match of the given pattern must be a link: ERCS/erc-165.md#L96
error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-165.md | 96 | 1. If you are not sure if the contract implements ERC-165, use the above procedure to confirm. | = info: the pattern in question: `(?i)(?:eip|erc)-([0-9])+`
the first match of the given pattern must be a link: ERCS/erc-165.md#L97
error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-165.md | 97 | 2. If it does not implement ERC-165, then you will have to see what methods it uses the old-fashioned way. | = info: the pattern in question: `(?i)(?:eip|erc)-([0-9])+`
the first match of the given pattern must be a link: ERCS/erc-165.md#L98
error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-165.md | 98 | 3. If it implements ERC-165 then just call `supportsInterface(interfaceID)` to determine if it implements an interface you can use. | = info: the pattern in question: `(?i)(?:eip|erc)-([0-9])+`
the first match of the given pattern must be a link: ERCS/erc-165.md#L106
error[markdown-link-first]: the first match of the given pattern must be a link --> ERCS/erc-165.md | 106 | The mechanism described above (with `0xffffffff`) should work with most of the contracts previous to this standard to determine tha... | = info: the pattern in question: `(?i)(?:eip|erc)-([0-9])+`
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'
HTMLProofer
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101

Artifacts

Produced during runtime
Name Size
pr_number
435 Bytes