fix: minor refactor of left over code from migration

[aversini]

Summary by CodeRabbit

• Tests

  • Updated descriptions for utility function tests for clarity.

• Chores

  • Removed unused CSS class constants to streamline the UI system.

[coderabbitai]

Walkthrough

The changes involve a minor update to a test description in the UI system's utilities and a significant removal of constants related to UI components. This suggests a shift in how UI elements and layouts are defined, possibly moving towards a more dynamic or different approach to styling and grid system management.

Changes

File Path	Change Summary
.../__tests__/utilities.test.ts	Updated test description for twPlugin utility from "should work" to "should be defined".
.../common/constants.ts	Removed CSS class constants for UI elements (buttons, text inputs, etc.) and FLEXGRID_MAX_COLUMNS.

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[github-actions]

Bundle Size (components)

Status	File	Size (Gzip)	Limits
✅	style.css	6.98 KB	8 KB
✅	index.js	18.62 KB	20 KB
✅	vendor.js	65.07 KB	67 KB

Overall bundle size: 90.66 KB
Overall status: ✅

Bundle Size (system)

Status	File	Size (Gzip)	Limits
✅	style.css	2.83 KB (-104 B -3.46%)	4 KB
✅	index.js	1.74 KB	3 KB
✅	vendor.js	44.49 KB	46 KB

Overall bundle size: 49.06 KB (-104 B -0.21%)
Overall status: ✅

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: .coderabbit.yaml

Commits

Files that changed from the base of the PR and between 4da0100 and 6f4fcaf.

Files selected for processing (2)

• packages/ui-system/src/tests/utilities.test.ts (1 hunks)
• packages/ui-system/src/common/constants.ts (1 hunks)

Additional comments: 2

packages/ui-system/src/common/constants.ts (1)

• 1-3: The removal of various CSS class constants and the FLEXGRID_MAX_COLUMNS constant suggests a significant cleanup. It's essential to ensure that there are no lingering references to these removed constants elsewhere in the codebase, as such references could lead to runtime errors or broken UI components. Consider performing a thorough search across the project to verify that all references to the removed constants have been updated or removed accordingly.

packages/ui-system/src/__tests__/utilities.test.ts (1)

• 4-4: The update to the test description from "should work" to "should be defined" enhances the clarity and specificity of what the test aims to verify. This change aligns with best practices for test documentation by making the test's purpose more explicit.