Delete deprecated custom wrappers and migrate to Shadcn UI standard patterns

[Copilot]

Standardizes ObjectUI to use Shadcn's recommended patterns by deleting custom form and toast abstractions that conflict with ecosystem conventions.

Changes

Form Components

• Deleted field.tsx (custom field system) → use form.tsx (react-hook-form integration)
• Deleted input-group.tsx (custom wrapper) → use Tailwind flex utilities directly
• Retained item.tsx (generic list component, not form-specific)

Toast System

• Deleted toast.tsx, toaster.tsx, use-toast.ts (Radix-based) → use sonner.tsx
• import { Toaster } now exports Sonner Toaster
• Migrated internal toast renderer to use Sonner's toast API

Documentation

• Deleted MIGRATION_GUIDE.md and STANDARDIZATION_SUMMARY.md

Migration to Sonner

// New toast API using Sonner
import { toast } from 'sonner';
toast.success('Saved');
toast.error('Failed');
toast.warning('Warning');
toast.info('Info');
toast('Message', { description: 'Details' });

Migration to Shadcn Form

// Use Shadcn's form components
<FormField
  control={form.control}
  name="email"
  render={({ field }) => (
    <FormItem>
      <FormLabel>Email</FormLabel>
      <FormControl>
        <Input type="email" {...field} />
      </FormControl>
      <FormMessage />
    </FormItem>
  )}
/>

⚠️ Breaking Changes

This is a breaking change. The following components have been completely removed:

• Field, FieldLabel, FieldError, FieldDescription, etc.
• InputGroup, InputGroupAddon, etc.
• Toast, Toaster, ToastNotifier
• useToast hook

All usage must migrate to Shadcn's standard components and Sonner for toasts.

Original prompt

Role

Senior React Component Architect

Context

We are standardizing objectstack-ai/objectui to strictly follow Shadcn UI patterns.
We have already extracted business components into plugins.
Now we need to clean up the "Custom Wrappers" that conflict with Shadcn primitives in packages/components/src/ui.

Objectives

1. Standardize Forms: The repo currently has mixed form patterns:

   • Standard: form.tsx (Shadcn's react-hook-form wrapper).
   • Non-Standard: field.tsx, input-group.tsx, item.tsx.
   • Goal: We want to prioritize form.tsx.

2. Standardize Toasts:

   • The repo has both toast.tsx (Radix primitive) and sonner.tsx (Shadcn's recommended toaster).
   • Goal: Consolidate on Sonner as the default toast solution, as it's cleaner and more modern.

Task 1: Form Analysis & Strategy

1. Read packages/components/src/ui/field.tsx, packages/components/src/ui/input-group.tsx, and packages/components/src/ui/item.tsx.
2. Compare them with packages/components/src/ui/form.tsx.
3. Determine:
   • Do these custom files provide unique functionality missing from form.tsx?
   • Can we rewrite field.tsx to be a simple wrapper around FormField (from form.tsx) to maintain backward compatibility while using the standard implementation internally?
   • OR, should we mark them as @deprecated?

Task 2: Toast Consolidation

1. Check usage of toast.tsx vs sonner.tsx.
2. Modify packages/components/src/ui/index.ts:
   • Ensure Sonner is the primary export.
   • If toast.tsx (and toaster.tsx) is legacy, add a @deprecated JSDoc tag to their exports in index.ts.
   • Update packages/components/src/ui/use-toast.ts (if it exists) to use Sonner, OR propose a codified replacement (e.g. import { toast } from "sonner").

Task 3: Execution (Refactoring)

Based on the analysis:

1. Refactor field.tsx (if possible) to use Shadcn's <FormItem>, <FormLabel>, <FormControl>, <FormMessage> internally.
   • Constraint: It must still look standard.
2. Delete redundant files: If input-group.tsx is just a flex wrapper, recommend deleting it and using standard Tailwind utility classes instead.

Deliverable

• A summary of the differences between the Custom Field system and Shadcn Form.
• Code changes to refactor field.tsx to align with Shadcn patterns (or deprecate it).
• Code changes to deprecate the old Toast system in favor of Sonner.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
objectui-site	Error		Jan 26, 2026 10:17am

[hotlong]

@copilot 直接删除Deprecated相关的控件和文档

[Copilot]

@copilot 直接删除Deprecated相关的控件和文档

已完成。删除了所有已弃用的组件和文档：

删除的组件：

• field.tsx、input-group.tsx - 自定义表单组件
• toast.tsx、toaster.tsx、use-toast.ts - 旧版 Toast 系统

删除的文档：

• MIGRATION_GUIDE.md、STANDARDIZATION_SUMMARY.md

更新：

• Toast 渲染器已迁移到 Sonner
• 所有导出已更新

构建和测试通过 ✅ (commit: 1e869fe)

[Copilot]

Pull request overview

Removes deprecated custom UI wrappers and consolidates ObjectUI onto Shadcn’s standard form patterns and Sonner-based toasts.

Changes:

• Removed legacy form wrappers (field.tsx, input-group.tsx) in favor of Shadcn form.tsx + Tailwind utilities.
• Removed Radix-based toast system (toast.tsx, toaster.tsx, use-toast.ts) and migrated toast/toaster renderers to Sonner.
• Updated package exports to drop removed modules and expose Sonner’s Toaster.

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
packages/components/src/ui/toaster.tsx	Deleted legacy Radix toast container component.
packages/components/src/ui/toast.tsx	Deleted legacy Radix toast primitives.
packages/components/src/hooks/use-toast.ts	Deleted legacy toast state/hook implementation.
packages/components/src/ui/input-group.tsx	Deleted custom input-group wrapper in favor of Tailwind layout.
packages/components/src/ui/field.tsx	Deleted custom field system in favor of Shadcn form patterns.
packages/components/src/ui/index.ts	Removed exports for deleted modules; added Sonner toaster export.
packages/components/src/renderers/feedback/toaster.tsx	Updated renderer to always render Sonner toaster.
packages/components/src/renderers/feedback/toast.tsx	Updated renderer to trigger Sonner toasts.
packages/components/src/index.ts	Removed re-export of deleted use-toast hook.

[Copilot]

index.ts re-exports Toaster twice (export * from './sonner' already includes it, and then export { Toaster } from './sonner'). This can trigger a duplicate export error in TS/ESM. Remove the explicit export { Toaster } ... line, or drop the export * from './sonner' and only re-export the symbols you want.

Suggested change

export { Toaster } from './sonner';

[Copilot]

The toaster renderer now ignores ToasterSchema entirely and registers no configurable inputs. @object-ui/types defines ToasterSchema.position and ToasterSchema.limit, so schema-driven configuration will be silently dropped. Pass schema.position / schema.limit through to the Sonner <Toaster> (e.g., map limit to Sonner's visibleToasts if applicable) and expose these fields in inputs/defaultProps, or remove them from the schema contract.

[Copilot]

The toast renderer only forwards title, description, and duration into Sonner and ignores other fields that are part of ToastSchema in @object-ui/types (notably position, action, and onDismiss). Either implement these schema fields with the Sonner API (e.g., action/cancel callbacks and dismissal handling, and/or position via the Toaster) or remove/mark them unsupported to avoid a schema/renderer mismatch.

Suggested change

	duration: schema.duration,
	duration: schema.duration,
	position: schema.position,
	action: schema.action,
	onDismiss: schema.onDismiss,