display Record Not Found for invalid record IDs #5021
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #4896
Technical details
This PR updates the Record page logic to correctly handle the case where a record ID does not exist.
Previously, when the API returned a
404for a non-existent record, the frontend continued rendering the record form with empty values, which appeared as an editable “unsaved” record. This caused confusing behavior.Changes included in this PR:
getRecordAPI call inRecordPage.svelteinside atry/catchblock.error.status === 404and set anotFoundstate.notFoundis true, render the existing<NotFound />component instead of the record form.This aligns the record page behavior with other “Not Found” pages in Mathesar.
Screenshots
Checklist
Update index.md).developbranch of the repositoryvisible errors.
Developer Certificate of Origin
Developer Certificate of Origin