fix(cli): Incorrect message on listing projects

[mrswastik-robot]

User description

Description

This PR corrects the invalid message displayed while listing projects with cmd - keyshade project list my-workspace

Fixes #621

Screenshots of relevant screens

Change is done on the list.projects.ts file:

Developer's checklist

• My PR follows the style guidelines of this project
• I have performed a self-check on my work

If changes are made in the code:

• I have followed the coding guidelines
• My changes in code generate no new warnings
• My changes are breaking another fix/feature of the project
• I have added test cases to show that my feature works
• I have added relevant screenshots in my PR
• There are no UI/UX issues

Documentation Update

• This PR requires an update to the documentation at docs.keyshade.xyz
• I have made the necessary updates to the documentation, or no documentation changes are required.

---

PR Type

Bug fix

---

Description

• Corrected the error message when no projects are found.

• Updated the CLI output for better clarity.

---

Changes walkthrough 📝

	Relevant files
Bug fix	list.project.ts Corrected CLI message for empty project list                          apps/cli/src/commands/project/list.project.ts Updated the error message from "No forks found" to "No projects found". Ensured the correct message is displayed when no projects are listed. +1/-1

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[codiumai-pr-agent-free]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis ✅ 621 - Fully compliant Compliant requirements: Fix incorrect error message when listing projects Message should display "No projects found" instead of current message

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No major issues detected

[codiumai-pr-agent-free]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Possible issue	Fix array length check inconsistency to prevent potential undefined behavior The code uses projects.length to check array size but iterates over data.items. This inconsistency could cause bugs. Use data.items.length instead for the length check. apps/cli/src/commands/project/list.project.ts [41-44] -if (projects.length > 0) { +if (data.items.length > 0) { data.items.forEach((project: any) => { Logger.info(`- ${project.name} (${project.slug})`) }) } Apply this suggestion Suggestion importance[1-10]: 8 Why: The inconsistency between using 'projects.length' for the check but 'data.items' for iteration could lead to runtime errors if these arrays are different. This is a significant bug risk that should be addressed.	8
General	Improve type safety by replacing any type with proper interface definition Replace the any type with a proper interface or type definition for the project object to ensure type safety. apps/cli/src/commands/project/list.project.ts [42-43] -data.items.forEach((project: any) => { +interface Project { + name: string; + slug: string; +} +data.items.forEach((project: Project) => { Logger.info(`- ${project.name} (${project.slug})`) }) Apply this suggestion Suggestion importance[1-10]: 4 Why: While adding type definitions improves code maintainability and catches potential type-related bugs early, this suggestion is primarily about code quality rather than fixing a critical issue.	4

[rajdip-b]

🎉 This PR is included in version 2.9.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀