Files
GiselleNessi bd17c08891 Fix/feedback api endpoints (#8024)
<!--

## title your PR with this format: "[SDK/Dashboard/Portal] Feature/Fix: Concise title for the changes"

If you did not copy the branch name from Linear, paste the issue tag here (format is TEAM-0000):

## Notes for the reviewer

Anything important to call out? Be sure to also clarify these in your comments.

## How to test

Unit tests, playground, etc.

-->

<!-- start pr-codex -->

---

## PR-Codex overview
This PR focuses on enhancing input validation and error handling in the `submitSupportFeedback` and `checkFeedbackStatus` functions, as well as improving the `SupportCaseDetails` component for better user experience during feedback submission.

### Detailed summary
- Improved input validation in `submitSupportFeedback` for `ticketId` and `rating`.
- Enhanced error handling with more specific error messages.
- Added comprehensive validation for API response structure.
- Updated `SupportCaseDetails` to handle status check errors non-blockingly.
- Adjusted feedback submission logic to improve user experience and error reporting.
- Refactored button and feedback display logic for clarity and usability.

> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`

<!-- end pr-codex -->

<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit

* **New Features**
  * Interactive 5‑star rating, accessible controls, auto‑resizing feedback textarea, and integrated Send Feedback button with spinner.
  * “Checking feedback status…” loader and clear “Thank you” state after successful submission.

* **Improvements**
  * Non‑blocking status check with a user‑facing warning if verification fails.
  * Faster, clearer error messages and timeouts for network/server issues; form validation prevents invalid submissions.
  * Feedback resets and success toasts on submission.

* **Bug Fixes**
  * Feedback UI no longer fails when status verification errors occur; malformed API responses handled gracefully.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2025-09-11 09:03:02 +00:00
..
2025-09-11 09:03:02 +00:00
2025-02-24 22:16:02 -07:00
2024-06-18 22:42:01 -07:00
2025-07-03 18:32:04 -07:00
2025-06-20 16:14:38 -07:00
2025-06-20 16:14:38 -07:00
2024-06-18 22:42:01 -07:00
2025-06-20 16:14:38 -07:00
2025-06-20 16:14:38 -07:00

thirdweb.com

This repo contains the full source for all of thirdweb.com and the thirdweb dashboard.

Starting a local dev server

Run from the root folder (thirdweb-dev/js):

cd <path/to/thirdweb-dev/js>
pnpm dashboard

Building for production

pnpm build

Environment Variables

Some env vars can be overridden that are required for some external services to work. You can find them in the .env.example file at the root level of the project including some descriptions of what they are used for.

To define env vars please create a .env file based on the .env.example template at the root level of the project. This file is ignored by git so you can safely add it to your local copy of the project.

Add your thirdweb clientID and secret key to build a basic functioning version of the site.

Code Structure and Style Guide

Components

  • Components should go in a components folder next to the app page they are used in.
  • If a component is reused in multiple pages, it should go in the lowest level route folder it is used in. For example, if a chart component is used in all analytics subroutes /analytics/..., it should go in the /analytics/components folder.
  • All low-level components such as buttons, inputs, etc. should be shadcn components found in @/ui.
  • All composed components reused across all page routes are blocks, and should also go in the @/ui folder.

Data fetching

  • Use RSC wherever possible.
  • Write data fetching code in its own function in the same file as the component it is used in, not exported.
  • If the same data fetching function is used in multiple components, place it in a file in an api folder at the lowest level possible (just like components). If you need to do this you probable aren't organizing your components properly.