fix: reorganized data structure and introduced component classes

[MinCrohn]

• Introduced new fields—children, attrs, item—to overhaul the data structure and updated the README.
• Renamed the saveToHistory option to history and adjusted usage examples.
• Reimplemented components such as Background, Bar, Icon, and Text as classes with new validation logic.
• Added element classes (Grid, Group, Item, Relations) to improve grid updates.
• Made Zod schemas more granular to strengthen type definitions.

[gemini-code-assist]

Summary of Changes

Hello @MinCrohn, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request represents a significant architectural overhaul, transitioning from a configuration-driven approach to a more robust, class-based system for managing display elements and components. It introduces new data fields, renames existing ones for clarity, and enhances type safety through granular Zod schemas, aiming for improved maintainability and extensibility.

Highlights

• Data Structure Overhaul: The pull request introduces significant changes to the core data structure by adding new fields like children, attrs, and item. This standardizes how elements are nested and configured, moving away from a more generic config object.
• Class-Based Components & Elements: Key display components (Background, Bar, Icon, Text) and top-level elements (Grid, Group, Item, Relations) have been reimplemented as dedicated classes. This improves encapsulation, modularity, and streamlines their update logic.
• Enhanced Type Safety & Validation: The project now leverages more granular Zod schemas for all data structures, including new primitive types for colors, sizes, and margins. This ensures stricter type definitions, robust runtime validation, and better developer experience.
• API Renaming & Simplification: The saveToHistory option has been renamed to history for clarity. Internal update mechanisms are streamlined, with properties now often assigned directly rather than through a nested config object, simplifying property access and modification.
• Legacy Data Conversion: The PR includes updated logic to convert older data formats to the new, reorganized structure, ensuring backward compatibility for existing data.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a significant and well-structured refactoring of the library's core data structures and component handling. The move to class-based elements and components, along with more granular and strict Zod schemas, is a major improvement for maintainability and developer experience. The new TypeScript definitions are especially commendable for their clarity and detailed examples. I've identified a few areas with potential issues, ranging from critical correctness bugs to maintainability concerns. My review focuses on ensuring state consistency, correcting logic, and improving code clarity. Addressing these points will help solidify this new architecture.

[MinCrohn]

/gemini review

[gemini-code-assist]

Code Review

This pull request introduces a major refactoring of the library's core architecture, moving to an object-oriented design. Key improvements include data validation using Zod, a structured component model, and better code organization. The new TypeScript definitions and updated tests improve maintainability. The review focuses on a critical bug in line rendering, a potential issue in a utility function, and a documentation recommendation.

[MinCrohn]

/gemini review

[gemini-code-assist]

Code Review

The code changes introduce a new class-based system with mixins for components and elements, which improves modularity, extensibility, and clarity. The data structure has been overhauled, and granular Zod schemas with custom validation for ID uniqueness have been introduced, enhancing robustness and developer experience. Documentation updates, including the detailed data.d.ts file and README examples, are helpful for users. There is one high-severity correctness issue in the new update logic that should be addressed.

[MinCrohn]

/gemini review

[gemini-code-assist]

Code Review

This pull request refactors the data structure and rendering logic, moving to class-based elements/components with a mixin-based update system. The new Zod schemas enhance type safety. There's a critical bug in grid rendering and two high-severity issues related to potential memory leaks when updating children/components.

[MinCrohn]

/gemini review

[gemini-code-assist]

Code Review

This is an impressive and comprehensive refactoring. The shift to a class-based architecture with mixins for both elements and components greatly improves modularity and extensibility. The new data structure, backed by granular Zod schemas and detailed TypeScript definitions, significantly enhances type safety and developer experience.

I've identified one critical issue where a function signature change was not propagated to all its call sites, which will break the array update logic. I've also noted a medium-severity issue regarding DOM style manipulation that could be made more robust.

Overall, this is a very high-quality pull request that modernizes the library's architecture and sets a strong foundation for future development. Excellent work!