-
Notifications
You must be signed in to change notification settings - Fork 697
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
Comments
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? |
Depends on how fast it merges 😆 maybe just try with a single pallet first if it works? |
We are in the monorepo now @sacha-l |
We should first install link checker (#993) to make sure this fix is worthwhile. |
@kianenigma part of the issue to address here is that what's currently in the READMEs is outdated from some point in time when 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 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. |
The link checker is added. All the broken links are not fixed in the CI (see issue). |
I ran lychee for fun, FWIW here's a random selection of broken links (non-exhaustive):
|
transactionWatch: Remove the broadcast event
* forward message id to destination chain * fix import
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
polkadot-sdk/.config/lychee.toml
Line 29 in a706171
The text was updated successfully, but these errors were encountered: