Skip to content

docs(how-to/file-route-conventions): add "Catch-all Route" section #13769

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

Merged
merged 2 commits into from
Jun 6, 2025

Conversation

davidbielik
Copy link
Contributor

followup to #13764 to document 404 with file routing

Copy link

changeset-bot bot commented Jun 6, 2025

⚠️ No Changeset found

Latest commit: 85a3176

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@timdorr
Copy link
Member

timdorr commented Jun 6, 2025

Thanks!

@timdorr timdorr merged commit 05d986e into remix-run:main Jun 6, 2025
1 check passed
@davidbielik
Copy link
Contributor Author

davidbielik commented Jun 6, 2025

@timdorr do you know how to set this route to always return 404 status code? Would that just be done in its loader I assume?

export const loader = async ({ request }: Route.LoaderArgs) => {
  return data({}, 404);
};

@MichaelDeBoey MichaelDeBoey changed the title 404 route to file routing doc docs(how-to/file-route-conventions): add "Catch-all Route" section Jun 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants