Files
MananTank b371bf9630 Dashboard: Published Contract page UI improvements, Fix audit link (#7735)
<!--

## 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 improving the handling of IPFS URLs, enhancing the user interface, and refactoring components for better readability and maintainability. It includes updates to various components and functions to streamline the codebase and improve functionality.

### Detailed summary
- Changed `shortenString` default parameter from `true` to `false`.
- Updated `SelectTrigger` to have a `w-fit` class.
- Replaced `replaceIpfsUrl` with `publicIPFSGateway` and `resolveSchemeWithErrorHandler` in multiple components.
- Modified `ContractFunctionsOverview` to remove `onlyFunctions` prop.
- Updated UI elements for consistency and better spacing.
- Refactored `PublisherHeader` to `PublisherLink` for clarity.
- Enhanced `PublishedContract` component layout and structure.
- Added account address handling in multiple components.
- Improved error handling and logging in IPFS URL resolution.

> ✨ 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**
  * Added an "Edit" button to contract headers, visible only to the publisher when viewing their own contract.
  * Publisher information is now displayed with a more compact and streamlined UI.

* **UI Improvements**
  * Enhanced styling for contract headings, buttons, and function panels for better readability and consistency.
  * Updated publisher and contract layouts for improved clarity and usability.
  * Improved tab logic and feedback in contract function panels, including clearer "No inputs required" messaging.
  * Adjusted layout widths and border styles for published contract pages.
  * Refined link styling and layout in platform fee information sections.
  * Modified version selector width behavior for better fit.

* **Bug Fixes**
  * Updated IPFS URL handling for images and links, ensuring more reliable and consistent resolution.

* **Refactor**
  * Simplified and consolidated publisher and contract components for maintainability.
  * Replaced or removed deprecated utility functions for URL resolution.
  * Streamlined function panel logic and removed unnecessary props.
  * Refactored publisher header component to a more compact link-based design.

* **Chores**
  * Updated internal utility defaults (e.g., string shortening behavior) to improve display consistency.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2025-07-28 18:49:17 +00:00
..
2025-06-11 23:24:45 -07: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
2025-06-20 16:14:38 -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.