-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Linter for mdn_url #5201
Comments
As per @vinyldarkscratch's request, I started writing a linter for all MDN URLs in all folders and here are odd URLs I don't know what to do about:
|
@sideshowbarker I noticed you filed #5256 and #5257, which actually help with linter (since they fix some values that linter would fail on). If you are interested, here are some more similar issues (some of these might be false positives): × api\MediaKeyStatusMap.json -- #5269
× api\PaintWorkletGlobalScope.json
× api\Selection.json -- false positive, may be?
× api\ServiceWorkerRegistration.json
× html\elements\html.json
× html\elements\iframe.json
× http\data-url.json
× javascript\builtins\Object.json
× javascript\builtins\Promise.json
× webextensions\api\cookies.json
|
Thanks — I’ll be happy to raise PRs for those |
Speaking of which, @bershanskiy, would you be willing to re-share your linter code (particularly in the form of a PR), since we repurposed the original PR for just the API folder updates? |
@vinyldarkscratch
Done! #5273 |
I'm going to close this in favor of #5201 which suggests to test for broken links. |
Sometimes the
__compat.mdn_url
property is incorrect, e.g. as shown in #5195. After seeing that issue, I looked for more similar bugs and found a couple, so I propose we make an explicit linter check formdn_url
. Below is a draft checklist, please tell me if it sounds reasonable.Checks
api.feature
has a linkhttps://developer.mozilla.org/docs/Web/API/feature
E.g.
api.feature.attribute
has a linkhttps://developer.mozilla.org/docs/Web/API/feature/attribute
andapi.feature.feature_event
has linkhttps://developer.mozilla.org/docs/Web/API/feature/feature_event
The text was updated successfully, but these errors were encountered: