Return proper Response object in Pages function #149
Merged
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.
When converting to React Router 7, while trying to address some TypeScript typing issues, I made the mistake of not returning a proper
Response
object in the/collect
Pages handler.This meant that
/collect
was 1) writing the data, but 2) returning a 500 afterwards, which likely led to a host of issues like not settingIf-Modified-Since
headers properly (refs #148). This bug didn't appear in tests, nor using the Vite development server, which I mostly use for local development.This highlights how the Pages function handlers need to be covered by tests, but on the flip side, they're being removed on the
v3
branch underway.