chore(lint): fix lint error

[Shabi-x]

Summary by CodeRabbit

Release Notes

• Documentation

  • Updated documentation structure with new component categories

• Improvements

  • Enhanced Image component by removing click event handler
  • Improved List component with semantic HTML structure and more robust key generation

• Chores

  • Minor file maintenance in documentation and package configuration

These updates focus on refining component implementations and documentation organisation.

[coderabbitai]

Walkthrough

This pull request involves updates to documentation and component structure across multiple files. The changes primarily focus on improving the semantic structure of list and image components, updating the documentation metadata, and making minor file formatting adjustments. The modifications aim to enhance the consistency and standard compliance of the component library.

Changes

File	Change Summary
docs/components/_meta.json	Added array ["index", "image", "list", "resume_header"], added trailing newline
packages/components/image/Image.tsx	Removed onClick prop handling from image component
packages/components/list/list.tsx	Refactored list component to use semantic HTML (<ul> and <li>), updated ref type and key generation
packages/components/package.json	Added trailing newline

Possibly related PRs

• refactor: remove storybook config #50: Contains identical changes to the docs/components/_meta.json file array

Poem

🐰 Hop, hop, through components we go,
Semantic lists and images in tow,
Clicking fades, structure grows bright,
Code refactored with rabbit's delight!
Clean and crisp, our changes take flight 🚀

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• 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 testing code 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• 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/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

packages/components/list/list.tsx (1)

17-17: Consider performance implications of crypto.randomUUID().

While using crypto.randomUUID() ensures unique keys, generating UUIDs on every render might impact performance for large lists. Consider using a stable identifier from your data items if available.

-            <li key={crypto.randomUUID()}>{renderItem(item, index)}</li>
+            <li key={item.id ?? index}>{renderItem(item, index)}</li>

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 089b640 and 856530d.

📒 Files selected for processing (5)

• docs/components/_meta.json (1 hunks)
• docs/components/_meta.json (1 hunks)
• packages/components/image/Image.tsx (1 hunks)
• packages/components/list/list.tsx (1 hunks)
• packages/components/package.json (1 hunks)

✅ Files skipped from review due to trivial changes (3)

• packages/components/package.json
• docs/components/_meta.json
• docs/components/_meta.json

🔇 Additional comments (2)

packages/components/list/list.tsx (1)

12-12: LGTM! Improved semantic HTML structure.

The change from HTMLDivElement to HTMLUListElement and the corresponding switch to <ul> improves semantic HTML structure, making the component more accessible and standards-compliant.

Also applies to: 15-15

packages/components/image/Image.tsx (1)

6-6: LGTM! Clean props destructuring after lint fix.

The removal of the unused onClick prop helps maintain a cleaner codebase by eliminating dead code. This aligns well with the lint fix objectives.

Let's verify if there are any remaining onClick handlers on img elements that might need similar cleanup:

✅ Verification successful

OnClick clean-up in the Image component is confirmed

Our verification has found that there are no remaining onClick handlers on any <img> elements within the codebase. The removal of the unused onClick prop from the destructuring in packages/components/image/Image.tsx aligns with the lint fix objectives and maintains cleaner code.

• File inspected: packages/components/image/Image.tsx
• No residual onClick usage on <img> elements detected

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for onClick handlers on img elements
ast-grep --pattern 'img {
  onClick={$_}
  $$$
}'

Length of output: 51

[fu050409]

Consider use git commit -S to sign up your commits later? I'll bypass this requirement this time.