We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is related to a bug I uncovered and reported in the Elm packages repo: elm/package.elm-lang.org#313
jfmengels/lint-debug/1.0.0
NoDebug
The problem is that the jfmengels/lint-debug/1.0.0 link links to https://package.elm-lang.org/packages/jfmengels/lint-debug/1.0.0, which is missing a trailing slash. In the README, the NoDebug link links to a relative URL ./NoDebug. Without the trailing slash in the URL, this links to https://package.elm-lang.org/packages/jfmengels/lint-debug/NoDebug, but we actually want to link to https://package.elm-lang.org/packages/jfmengels/lint-debug/1.0.0/NoDebug.
./NoDebug
Add a trailing slash to the link to the package.
Let me know if you would like help with fixing this.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
This is related to a bug I uncovered and reported in the Elm packages repo: elm/package.elm-lang.org#313
SSCCE
jfmengels/lint-debug/1.0.0
NoDebug
link in the README (not the table of contents).Explanation
The problem is that the
jfmengels/lint-debug/1.0.0
link links to https://package.elm-lang.org/packages/jfmengels/lint-debug/1.0.0, which is missing a trailing slash. In the README, theNoDebug
link links to a relative URL./NoDebug
. Without the trailing slash in the URL, this links to https://package.elm-lang.org/packages/jfmengels/lint-debug/NoDebug, but we actually want to link to https://package.elm-lang.org/packages/jfmengels/lint-debug/1.0.0/NoDebug.Probable solution
Add a trailing slash to the link to the package.
Let me know if you would like help with fixing this.
The text was updated successfully, but these errors were encountered: