fix(api/services): strip internal fields from public response#2
Open
fix(api/services): strip internal fields from public response#2
Conversation
Strip internal fields from public response in service retrieval.Previously /api/services returned the full DB row to unauthenticated clients, leaking wholesale costPrice and upstreamPrice margin data, priceLocked flag, and internal numeric ids. Both the main enrichment path and the catch fallback now destructure out the sensitive fields before responding.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
whogf22
added a commit
that referenced
this pull request
Apr 30, 2026
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.
Strip internal fields from public response in service retrieval.Previously /api/services returned the full DB row to unauthenticated clients, leaking wholesale costPrice and upstreamPrice margin data, priceLocked flag, and internal numeric ids.
Both the main enrichment path and the catch fallback now destructure out the sensitive fields before responding.