Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update EIP-721: delete broken openzeppelin links #5903

Closed
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion EIPS/eip-721.md
Original file line number Diff line number Diff line change
Expand Up @@ -440,7 +440,6 @@ XXXXERC721, by William Entriken -- a scalable example implementation
1. Curio Cards. https://mycuriocards.com
1. Rare Pepe. https://rarepepewallet.com
1. Auctionhouse Asset Interface. https://github.com/dob/auctionhouse/blob/master/contracts/Asset.sol
1. OpenZeppelin SafeERC20.sol Implementation. https://github.com/OpenZeppelin/zeppelin-solidity/blob/master/contracts/token/ERC20/SafeERC20.sol
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the contribution!
This is a historical doc, to fix it

  1. Editors are working on a link policy per EIP-5757 (Add EIP-5757: Propose process for allowing external links #5757 ), let's wait for that to be finalized
  2. Links are generally suggested to use permlink to reduce chance of such broken links in the future

But still, thank you for your contribution! Greatly appreciated

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@xinbenlv Yes. Exactly. This EIP is referenced by many people and we should wait for the Editors reply as it is a change to a part of that document.
I too recommend using permlink, but since the source of the change points to the default branch, I made the change using the same policy.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Links are generally suggested to use permlink to reduce chance of such broken links in the future

So, in this case, would the better fix be to replace the broken link with a permlink to the last SafeERC20, rather than a link to ERC721?

And, given these links are no normative, and this one is not discussed in the proposal, I'd be happy to see it removed.


## Copyright

Expand Down