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 /standards/types to /standards/types/ per linkchecker warning #2937

Merged
merged 1 commit into from
Oct 18, 2024

Conversation

tantek
Copy link
Contributor

@tantek tantek commented Oct 18, 2024

Linkchecker warns that links to https://www.w3.org/standards/types are redirected to https://www.w3.org/standards/types/ so fix the generation of these links to automatically avoid this warning.

…ards/types/ per linkchecker warning

Linkchecker warns that links to https://www.w3.org/standards/types are redirected to https://www.w3.org/standards/types/ so fix the generation of these links to automatically avoid this warning.
@tabatkins tabatkins merged commit 61fea1b into speced:main Oct 18, 2024
1 of 9 checks passed
@Ms2ger
Copy link
Contributor

Ms2ger commented Oct 28, 2024

I'm getting complaints seemingly in the opposite direction: https://labs.w3.org/echidna/api/status?id=03aca09e-4476-4b3d-933a-4cb62dd006c1

@tantek
Copy link
Contributor Author

tantek commented Oct 28, 2024

@Ms2ger looks like a specberus bug. Could you file it with that error message and this PR since Linkchecker was actually checking the link whereas it looks like specberus has an out of date rule that needs updating?

@tantek tantek deleted the patch-13 branch October 28, 2024 16:13
@Ms2ger
Copy link
Contributor

Ms2ger commented Oct 28, 2024

Thanks for the pointer, seems like it's w3c/specberus#1887

@anssiko
Copy link
Contributor

anssiko commented Nov 6, 2024

(Cross-linking: the Specberus bug w3c/specberus#1887 was fixed by w3c/specberus#1889)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants