[feature] Nice stuff I've built

[gocanto]

Summary by CodeRabbit

• New Features

  • Updated the projects page to display a single "Open Source / Client Projects" section with an improved introductory description.
  • Project cards are now rendered dynamically from a unified projects list.

• Enhancements

  • Each project now includes an indicator specifying if it is open source.
  • Project cards display associated icons for better visual identification.

• Refactor

  • Streamlined the projects page and project card components for easier future updates and improved maintainability.
  • Converted components to use the latest script setup syntax for improved code clarity and performance.
  • Updated project card links to open in new tabs with enhanced security attributes.

[coderabbitai]

Walkthrough

The changes refactor the projects page to use a reactive projects variable populated from the user store, replace static project arrays with dynamic data, add an introductory text block, and convert the script to <script setup lang="ts">. The Project interface and user response data are extended with isOpenSource and icon properties. The project card component is updated to use these new properties and refactored to <script setup> syntax.

Changes

File(s)	Change Summary
src/pages/ProjectsPage.vue	Converted to <script setup lang="ts">; removed static project arrays and icon imports; added intro text; renders projects reactively from user store data.
src/stores/users/response.ts	Added isOpenSource: boolean and icon: string properties to each project object; updated UUID of second project.
src/stores/users/userType.ts	Extended Project interface with isOpenSource: boolean and icon: string properties.
src/partials/ProjectCardPartial.vue	Refactored to <script setup lang="ts">; changed root element from <router-link> to <a>; updated bindings to use item.url and image(item.icon); renamed openSource to isOpenSource.

Poem

In the garden of code, a change takes root,
Projects now bloom with a dynamic pursuit.
“Is it open source?” the rabbits inquire,
With a hop and a skip, their curiosity won’t tire.
Script setup shines, the static fades away—
A fresh field for projects, in the sunniest way!
🐇✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

npm error Exit handler never called!
npm error This is an error with npm itself. Please report this error at:
npm error https://github.com/npm/cli/issues
npm error A complete log of this run can be found in: /.npm/_logs/2025-07-15T02_27_52_431Z-debug-0.log

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f2fdd9e and 3ce39b1.

📒 Files selected for processing (2)

• src/partials/ProjectCardPartial.vue (2 hunks)
• src/stores/users/response.ts (9 hunks)

🚧 Files skipped from review as they are similar to previous changes (2)

• src/partials/ProjectCardPartial.vue
• src/stores/users/response.ts

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @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: 2

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 287e4c9 and aae03df.

📒 Files selected for processing (3)

• src/pages/ProjectsPage.vue (2 hunks)
• src/stores/users/response.ts (10 hunks)
• src/stores/users/userType.ts (1 hunks)

🔇 Additional comments (5)

src/stores/users/userType.ts (1)

31-31: Clean interface extension for open source project identification.

The addition of the isOpenSource boolean property to the Project interface is well-structured and provides clear typing for the new feature.

src/stores/users/response.ts (1)

149-149: Consistent data implementation for open source project identification.

The isOpenSource property has been correctly added to all project objects, maintaining consistency with the interface extension. The pattern of having one non-open source project among predominantly open source projects aligns with typical developer portfolios.

Also applies to: 159-159, 169-169, 179-179, 189-189, 199-199, 209-209, 219-219, 229-229, 239-239

src/pages/ProjectsPage.vue (3)

22-32: Well-written introductory content for the projects page.

The new descriptive text effectively communicates the developer's experience and expertise, providing valuable context for visitors viewing the projects.

---

34-34: Improved section title reflects the unified project categorization.

The updated title "Open Source / Client Projects" clearly indicates the consolidated approach to displaying both types of projects.

---

70-70: Verify the Vue import path.

The import path ~node_modules/vue is unusual and may not work correctly. Standard Vue imports should use just 'vue'.

-import { onMounted, ref } from '~node_modules/vue';
+import { onMounted, ref } from 'vue';

Please verify this import works correctly in your build system, as the tilde prefix typically refers to the source directory root, not node_modules.

[coderabbitai]

Actionable comments posted: 2

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between aae03df and 0caf6f6.

⛔ Files ignored due to path filters (8)

• public/images/icons/icon-01.svg is excluded by !**/*.svg
• public/images/icons/icon-02.svg is excluded by !**/*.svg
• public/images/icons/icon-03.svg is excluded by !**/*.svg
• public/images/icons/icon-04.svg is excluded by !**/*.svg
• public/images/icons/icon-05.svg is excluded by !**/*.svg
• public/images/icons/icon-06.svg is excluded by !**/*.svg
• public/images/icons/icon-07.svg is excluded by !**/*.svg
• public/images/icons/icon-08.svg is excluded by !**/*.svg

📒 Files selected for processing (4)

• src/pages/ProjectsPage.vue (2 hunks)
• src/partials/ProjectCardPartial.vue (2 hunks)
• src/stores/users/response.ts (10 hunks)
• src/stores/users/userType.ts (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (3)

• src/stores/users/userType.ts
• src/stores/users/response.ts
• src/pages/ProjectsPage.vue

🔇 Additional comments (2)

src/partials/ProjectCardPartial.vue (2)

10-15: LGTM! Image handling improvement with helper function.

The image helper function provides better asset handling and the attributes are properly structured for accessibility.

---

17-17: Good naming convention improvement.

The property name change from item.openSource to item.isOpenSource follows better boolean naming conventions and aligns with the updated interface.