Revalidate server pages after registration + display dynamic pricing#921
Merged
Conversation
Server pages were serving stale data (resource counts, pricing) because Next.js cached the SSR output. Now all four registration paths call revalidatePath to bust the cache for the affected origin's server page.
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
8 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Two fixes for server page display issues:
1. Revalidate server pages after registration
/server/[id]) were serving stale data because Next.js cached the SSR outputrevalidatePathcalls after successful registration in all four registration paths (tRPC register, tRPC registerFromOrigin, REST register, REST register-origin)2. Display dynamic pricing from discovery metadata
/api/orders) showed "$300.00" instead of "Up to $300.00"scheme: exact. The discovery doc correctly sayspricingMode: "dynamic"but this was discarded during registrationpricingModefrom the discovery document, store it inResources.metadata, and use it inResourcePricingto detect dynamic pricing regardless of the 402 schemeTest plan