{ "$schema": "https://ui.shadcn.com/schema/registry-item.json", "name": "item", "title": "Item", "description": "A list item system with media, content, and actions.", "registryDependencies": [ "https://ds.formance.com/r/separator.json" ], "files": [ { "path": "registry/default/ui/item.tsx", "content": "import { cva, type VariantProps } from 'class-variance-authority';\nimport { Slot as SlotPrimitive } from 'radix-ui';\nimport * as React from 'react';\n\nimport { Separator } from '@/registry/default/ui/separator';\nimport { cn } from '@/lib/utils';\n\n// Stays a `div` with an explicit `role`: `Item` and `ItemSeparator` render\n// divs, and a `ul` may only contain `li`, so a real `ul` here is invalid HTML\n// and browsers drop the list semantics it was reached for. `Item` is also used\n// standalone (4 call sites), where an `li` would be just as wrong.\nfunction ItemGroup({ className, ...props }: React.ComponentProps<'div'>) {\n return (\n
\n );\n}\n\nfunction ItemSeparator({\n className,\n ...props\n}: React.ComponentPropsa:hover]:text-primary [&>a]:underline [&>a]:underline-offset-4',\n className\n )}\n {...props}\n />\n );\n}\n\nfunction ItemActions({ className, ...props }: React.ComponentProps<'div'>) {\n return (\n
\n );\n}\n\nfunction ItemHeader({ className, ...props }: React.ComponentProps<'div'>) {\n return (\n \n );\n}\n\nfunction ItemFooter({ className, ...props }: React.ComponentProps<'div'>) {\n return (\n \n );\n}\n\nexport {\n Item,\n ItemActions,\n ItemContent,\n ItemDescription,\n ItemFooter,\n ItemGroup,\n ItemHeader,\n ItemMedia,\n ItemSeparator,\n ItemTitle,\n};\n", "type": "registry:ui" } ], "type": "registry:ui" }