This repository provides a comprehensive component library for building admin dashboards and CRUD applications in React. It wraps react-admin's headless core (`ra-core`) with a shadcn/ui aesthetic, delivering over 80 reusable components including data table, forms, inputs, fields, buttons, layout elements, and a rich text editor. The architecture follows a provider pattern for data, authentication, and internationalization, making it backend-agnostic. It includes a demo e-commerce application, a Storybook for visual testing, a marketing website, and a shadcn registry for easy installation via the `shadcn add` command. The codebase is well-structured with extensive unit tests and documentation, though it depends on pre-release Base UI and several react-admin enterprise features that require a paid subscription.
This repository is a comprehensive React component library (`@ant-design/pro-components`) that provides enterprise-grade UI components built on top of Ant Design. It is not a standalone application but a library intended to be used as a dependency in React projects. The library includes high-level, opinionated components such as `ProTable`, `ProForm`, `ProLayout`, `ProCard`, `ProDescriptions`, `ProList`, and many more, designed to accelerate the development of complex admin panels, dashboards, and data-intensive user interfaces. The architecture is modular, with packages organized by domain (table, form, layout, card, field, etc.), and all components are exported from a single entry point. The library relies heavily on Ant Design v6, React 18+, and utilities like `dayjs`, `@dnd-kit`, `swr`, and `@rc-component/util`. The primary data flows involve asynchronous data fetching via `request` props (often using SWR for caching), controlled/uncontrolled state management, and extensive use of React context for internationalization, theme tokens, and form instance sharing. The library also includes a schema-driven form system (`BetaSchemaForm`), editable tables, drag-and-drop sorting, responsive layouts, and a comprehensive help system. It is well-documented with hundreds of demos and has a substantial test suite covering unit tests, integration tests, and edge cases.
e-virt-table is a high-performance, canvas-based virtual data table library designed for building spreadsheet-like grids in web applications. It renders tens of thousands of rows and columns using a custom canvas drawing engine with virtual scrolling, fixed columns, cell editing, selection, autofill, copy/paste, sorting, filtering, tree data, cell merging, and undo/redo. The library is framework-agnostic (usable in plain JS, Vue 2/3, and React) and is distributed as an npm package with UMD/ESM/CJS formats. Its architecture follows a modular event-driven pattern: a central Context class manages state and communication between subsystems (Selector, Editor, Database, Scroller, History, Validator, FinderBar, etc.), while a Paint module abstracts canvas drawing operations. The configuration surface is extensive (~100 options via CSS variables and a Config object), enabling deep customization of appearance and behavior. The repository also includes a bilingual VitePress documentation site with hundreds of interactive examples, as well as a dev playground and a suite of system-level tests for border rendering and scrollbar modes.
This is the source code for `@swimlane/ngx-datatable`, an Angular component library for building high-performance, feature-rich data tables. It provides virtual scrolling, client- and server-side sorting/paging, column reordering/resizing, row selection (single, multi, checkbox), tree view, row grouping, summary rows, and extensive custom template support. The library is built with Angular's signals-based reactivity and OnPush change detection, offering a modern reactive API. The repository also includes a comprehensive demo application and a test suite using Vitest, Angular CDK ComponentHarness, and Playwright for E2E. While the codebase demonstrates strong architectural patterns and reusable utilities, it suffers from a high number of open issues (917), some deprecated API surfaces, and a test stack in migration flux, indicating a mature but somewhat stale maintenance state.