Added a relay backed fallback for cache misses#269
Open
ayushshrivastv wants to merge 1 commit into
Open
Conversation
…ng URLs can still resolve when the listing isn’t yet available in the local DB/cache.
|
@ayushshrivastv is attempting to deploy a commit to the shopstr-eng Team on Vercel. A member of the Team first needs to authorize it. |
|
This pull request has been automatically marked as stale because it has not had recent activity for 3 weeks. |
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
1 participant
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.
The issue is split between pages/listing and utils/nostr/fetch-service.ts. Right now if a direct listing URL is not already available in the local DB/cache or hydrated product context, the page can still fail because there is no targeted relay lookup path for that listing identifier.
This change adds a relay-backed fallback for direct listing loads, so when the listing is missing from local cache/context, the page can fetch it directly from relays using the listing identifier, cache the fetched event, and then render it. It also keeps the stale-state reset behavior so old listing data does not block a new direct route from resolving correctly.