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

Fix all broken links #134

Open
ggwpez opened this issue Aug 14, 2023 · 7 comments
Open

Fix all broken links #134

ggwpez opened this issue Aug 14, 2023 · 7 comments
Labels
T1-FRAME This PR/Issue is related to core FRAME, the framework. T11-documentation This PR/Issue is related to documentation.

Comments

@ggwpez
Copy link
Member

ggwpez commented Aug 14, 2023

Using lychee link checker finds a few things. We should also add this to CI (#993).
cc @sacha-l

The list of broken links is in the CI

"https://docs.substrate.io/main-docs/build/custom-rpc/#public-rpcs",

@sacha-l
Copy link
Contributor

sacha-l commented Aug 15, 2023

Most of these are links from the auto-generated READMEs from years ago. I think the tool used was https://github.com/livioribeiro/cargo-readme. We should regenerate them as part of the upcoming docs work to improve the pallet rust docs / ensure they're updated with some CI job.

Anything to do before the repo merge though?

@ggwpez
Copy link
Member Author

ggwpez commented Aug 16, 2023

Anything to do before the repo merge though?

Depends on how fast it merges 😆 maybe just try with a single pallet first if it works?
But it could also be done after the monorepo.

@juangirini juangirini transferred this issue from paritytech/substrate Aug 24, 2023
@the-right-joyce the-right-joyce added T11-documentation This PR/Issue is related to documentation. T1-FRAME This PR/Issue is related to core FRAME, the framework. and removed I6-documentation labels Aug 25, 2023
@ggwpez
Copy link
Member Author

ggwpez commented Aug 29, 2023

We are in the monorepo now @sacha-l

@kianenigma
Copy link
Contributor

We should first install link checker (#993) to make sure this fix is worthwhile.

@Rashmirreddy Rashmirreddy moved this to To Do in Documentation Sep 11, 2023
@sacha-l
Copy link
Contributor

sacha-l commented Sep 13, 2023

@kianenigma part of the issue to address here is that what's currently in the READMEs is outdated from some point in time when cargo-readme was being used to auto-generate the READMEs from the Rust docs.

My suggestion is to start doing that again so that the READMEs for each pallet will be consistent with the Rust docs.

But having just tried that locally, the issue with using cargo-readme is that the links it takes from the Rust docs don't work as they are not URLs (they're inter-rustdoc-links). For e.g. the "See the [pallet] module for more information..." is not a valid link.

Screenshot 2023-09-13 at 11 16 45 AM

Another issue with using this tool is that none of the code generated by docify gets rendered. It may be worth customizing it for our needs here or rethinking how we want these READMEs to be generated altogether.

@ggwpez
Copy link
Member Author

ggwpez commented Oct 28, 2023

We should first install link checker (#993) to make sure this fix is worthwhile.

The link checker is added. All the broken links are not fixed in the CI (see issue).

@mrcnski
Copy link
Contributor

mrcnski commented Dec 18, 2023

I ran lychee for fun, FWIW here's a random selection of broken links (non-exhaustive):

[./docs/contributor/DOCUMENTATION_GUIDELINES.md]:
✗ [ERR] file:///Users/marcin/Repos/github.com/paritytech/polkadot-sdk/docs/contributor/CODEOWNERS | Failed: Cannot find file
✗ [ERR] file:///Users/marcin/Repos/github.com/paritytech/polkadot-sdk/docs/rustfmt.toml | Failed: Cannot find file

[./polkadot/roadmap/implementers-guide/src/messaging.md]:
✗ [404] https://research.web3.foundation/en/latest/polkadot/XCMP.html | Failed: Network error: Not Found

[./bridges/docs/high-level-overview.md]:
✗ [ERR] file:///Users/marcin/Repos/github.com/paritytech/polkadot-sdk/bridges/relays/bin-substrate/src/cli/relay_headers_and_messages | Failed: Cannot find file
✗ [ERR] file:///Users/marcin/Repos/github.com/paritytech/polkadot-sdk/bridges/relays/finality | Failed: Cannot find file
✗ [ERR] file:///Users/marcin/Repos/github.com/paritytech/polkadot-sdk/bridges/relays/messages | Failed: Cannot find file
✗ [ERR] file:///Users/marcin/Repos/github.com/paritytech/polkadot-sdk/bridges/relays/parachains | Failed: Cannot find file

[./substrate/frame/sudo/README.md]:
⧖ [TIMEOUT] https://docs.rs/pallet-sudo/latest/pallet_sudo/struct.GenesisConfig.html | Timeout

lexnv pushed a commit that referenced this issue Apr 3, 2024
transactionWatch: Remove the broadcast event
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 8, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 8, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 10, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 10, 2024
jonathanudd pushed a commit to jonathanudd/polkadot-sdk that referenced this issue Apr 10, 2024
claravanstaden pushed a commit to claravanstaden/polkadot-sdk that referenced this issue Sep 19, 2024
* forward message id to destination chain

* fix import
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T1-FRAME This PR/Issue is related to core FRAME, the framework. T11-documentation This PR/Issue is related to documentation.
Projects
Status: To Do
Status: Backlog
Development

No branches or pull requests

6 participants