All Projects → deadlinks → Cargo Deadlinks

deadlinks / Cargo Deadlinks

Licence: other
Cargo subcommand for checking your documentation for broken links

Programming Languages

rust
11053 projects

Labels

Projects that are alternatives of or similar to Cargo Deadlinks

Graphql Go Tools
Tools to write high performance GraphQL applications using Go/Golang.
Stars: ✭ 96 (-15.04%)
Mutual labels:  linter
Svlint
SystemVerilog linter
Stars: ✭ 103 (-8.85%)
Mutual labels:  linter
Import Linter
Import Linter allows you to define and enforce rules for the internal and external imports within your Python project.
Stars: ✭ 105 (-7.08%)
Mutual labels:  linter
Linter Farch
Make sure the filenames stay the same, control them! 👁
Stars: ✭ 101 (-10.62%)
Mutual labels:  linter
Linter Write Good
An Atom linter interface for write-good.
Stars: ✭ 102 (-9.73%)
Mutual labels:  linter
Doc8
Style checker for sphinx (or other) rst documentation.
Stars: ✭ 105 (-7.08%)
Mutual labels:  linter
Pre Commit Hooks
A set of useful (and documented!) git pre-commit hooks.
Stars: ✭ 95 (-15.93%)
Mutual labels:  linter
Abaplint
Standalone linter for ABAP
Stars: ✭ 111 (-1.77%)
Mutual labels:  linter
Luacheck
A tool for linting and static analysis of Lua code.
Stars: ✭ 1,382 (+1123.01%)
Mutual labels:  linter
Swiftdi
SwiftDI the new way to use your dependency in Swift 5.1
Stars: ✭ 107 (-5.31%)
Mutual labels:  linter
Eslint Plugin I18n Json
Fully extendable eslint plugin for JSON i18n translation files.
Stars: ✭ 101 (-10.62%)
Mutual labels:  linter
Rslint
A (WIP) Extremely fast JavaScript and TypeScript linter and Rust crate
Stars: ✭ 1,377 (+1118.58%)
Mutual labels:  linter
Wemake Python Styleguide
The strictest and most opinionated python linter ever!
Stars: ✭ 1,714 (+1416.81%)
Mutual labels:  linter
Nix Linter
Linter for the Nix expression language
Stars: ✭ 100 (-11.5%)
Mutual labels:  linter
Scopelint
scopelint checks for unpinned variables in go programs
Stars: ✭ 110 (-2.65%)
Mutual labels:  linter
Unimport
A linter, formatter for finding and removing unused import statements.
Stars: ✭ 96 (-15.04%)
Mutual labels:  linter
Gopherci
GopherCI was a project to help you maintain high-quality Go projects, by checking each GitHub Pull Request, for backward incompatible changes, and a suite of other third party static analysis tools.
Stars: ✭ 105 (-7.08%)
Mutual labels:  linter
Zoe
🌀 Zero-config ESLint toolchain with sensible defaults.
Stars: ✭ 113 (+0%)
Mutual labels:  linter
Yamllint
A linter for YAML files.
Stars: ✭ 1,750 (+1448.67%)
Mutual labels:  linter
Npm Package Json Lint
Configurable linter for package.json files
Stars: ✭ 106 (-6.19%)
Mutual labels:  linter

cargo-deadlinks • Crates.io License

Check your cargo doc documentation for broken links!

Useful if you just refactored the structure of your crate or want to ensure that your documentation is readable offline.

This crate pairs well with intra-doc links and cargo-intraconv, which make it easier to write links without having to know the exact HTML page rustdoc will generate.

deadlinks can also be used on projects that aren't Rust crates.

Installation

Install cargo-deadlinks via:

cargo install cargo-deadlinks

Alternatively, install pre-built binaries from the releases page.

Usage

From your packages directory run:

# this will automatically run `cargo doc` for you
# any broken links will show up in the output
cargo deadlinks
# if you also want to check http and https links
cargo deadlinks --check-http

By default cargo deadlinks will check only the offline (file://) links of your package.

If you want to check the documentation in another directory e.g. to check all your dependencies, you can provide the --dir argument:

cargo deadlinks --dir target/doc

To check a project that isn't a crate, use deadlinks instead:

# this requires that you already have a static site in build/html
deadlinks build/html

For information about other arguments run cargo deadlinks --help.

Minimum Supported Rust Version (MSRV)

The current MSRV is 1.45.0. This may be increased in minor versions, but will never increase in a patch version.

Contributing

We are happy about any contributions!

To get started you can take a look at our Github issues.

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as below, without any additional terms or conditions.

License

Licensed under either of

at your option.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].