Beta reactjs 404 & 500 Custom Error pages similarities
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 7.9k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
Both of error pages under beta/src/pages/{404,500}.js has the same component name and the module is exported.
404.js
export default function NotFound() {
return (
<Page toc={[]}>
<MarkdownPage meta={{title: 'Not Found'}}>
....
</MarkdownPage>
</Page>
);
}
500.js
export default function NotFound() {
return (
<Page toc={[]}>
<MarkdownPage meta={{title: 'Something Went Wrong'}}>
....
</MarkdownPage>
</Page>
);
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open beta/src/pages/404.js and beta/src/pages/500.js and compare their exported component declarations. Rename or otherwise distinguish the duplicated component names while preserving each page's existing behavior, then verify both custom error pages still render correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100