Update thunderstore-api to match up coming cyberstorm API changes

[Oksamies]

No description provided.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch 09-17-update_thunderstore-api_to_match_up_coming_cyberstorm_api_changes

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Oksamies]

• Separate and organize root.tsx to multiple files #1550
• Enable teams, team settigns and user settings pages #1544
• Correct API fetch params and data in few settings actions #1543
• Update thunderstore-api to match up coming cyberstorm API changes #1542 👈 (View in Graphite)
• Add forced currentUser update to settings and teams pages #1535
• Add a option to force currentUser update to getSessionCurrentUser #1541
• Ensure current user is updated #1540
• Fix session revalidation corner case #1539
• Fix setSsion stale value set #1538
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[graphite-app]

The requestSchema parameter is set to userLinkedAccountDisconnectRequestParamsSchema, but this appears to be a mismatch. This schema is defined for validating URL parameters, not the request body. Since the function doesn't send a request body (there's no body: JSON.stringify(data) in the request configuration), the requestSchema should be set to undefined. Alternatively, if request validation is needed, a proper request body schema should be defined separately from the URL parameter schema.

Suggested change

	requestSchema: userLinkedAccountDisconnectRequestParamsSchema,
	requestSchema: undefined,

Spotted by Diamond



Is this helpful? React 👍 or 👎 to let us know.

[VilppeRiskidev]

LGTM 👍

[graphite-app]

The requestSchema is set to userLinkedAccountDisconnectRequestDataSchema but the function no longer extracts or uses the 'data' parameter from props (line 15 only destructures config and params). This will cause the schema validation to fail since no request body data is being passed to apiFetch, but the schema expects a body with a 'provider' field. Either remove the requestSchema (set to undefined) or add back data extraction and body serialization.

Suggested change

	requestSchema: userLinkedAccountDisconnectRequestDataSchema,
	requestSchema: undefined,

Spotted by Diamond



Is this helpful? React 👍 or 👎 to let us know.