fix(social-ugig): use current gig input schema - #979
Open
WNZhao wants to merge 1 commit into
Open
Conversation
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.
Problem
social-ugigstill posts the legacy payload (content,tags, andprice_cents). The current uGigPOST /api/gigscontract requiresskills_required,budget_type, andlocation_type, with fixed prices represented bybudget_min/budget_max. Real non-dry-run publishing therefore receives a validation error instead of creating a gig.The old adapter also leaves listing intent ambiguous, which can place a seller offer in the hiring feed.
Fix
listing_type: for_hire, with an explicithiringoverrideskills_requireddefaultPriceCentsto dollar-valued fixed budgetsVerification
pnpm exec vitest run packages/social/ugig/src/index.test.ts --reporter=dot— 8/8 passedpnpm --filter @profullstack/sh1pt-social-ugig typecheck— passedpnpm --filter @profullstack/sh1pt-social-ugig build— passedgit diff --check— passedThe request fields and limits were checked against uGig's live
/openapi.json;listing_typewas additionally checked against the live create/edit UI payload and response model.