-
Notifications
You must be signed in to change notification settings - Fork 341
fix(docs): alert on 301, 303 links #3535
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
Conversation
|
| title: Link | ||
| description: Link renders an anchor element <a> by default and is primarily used for navigation. | ||
| ariaPattern: https://www.w3.org/WAI/ARIA/apg/patterns/link | ||
| ariaPattern: https://www.w3.org/WAI/ARIA/apg/patterns/link/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the difference between adding a / and not adding one?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
without /, it returns 301 and redirects to the one with /
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but it seems the docs.amplify.aws link example you are referencing is return 404 now 🥴
Now I see since you asked my last question. |

Description of changes
301, 303 status code should not be acceptable.
Note: We still double check 301 from docs.amplify.aws (code) because its broken link returns 301 (aws-amplify/docs#5221). e.g. 'https://www.w3.org/WAI/ARIA/apg/patterns/radtton' returns 404, but 'https://docs.amplify.aws/lib/auth/getarted/q/platform/js' returns 301
Issue #, if available
Description of how you validated changes
Checklist
yarn testpassessideEffectsfield updatedBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.