feat(platfrom): add delete method in api client

[kriptonian1]

User description

Description

Give a summary of the change that you have made

Fixes #[ISSUENO]

Dependencies

Mention any dependencies/packages used

Future Improvements

Mention any improvements to be done in future related to any file/feature

Mentions

Mention and tag the people

Screenshots of relevant screens

Add screenshots of relevant screens

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

enhancement

---

Description

• Added a delete method to the APIClient class in api-client.ts to support DELETE HTTP requests.
• The new method enhances the API client by allowing deletion operations, configured to handle credentials and JSON content types.

---

Changes walkthrough 📝

	Relevant files
Enhancement	api-client.ts Add DELETE Method to APIClient Class                                          apps/platform/src/lib/api-client.ts Added a new delete method to the APIClient class. The delete method sends a DELETE request to a specified URL and returns a promise with the response data. Configured the method to include credentials and set the 'Content-Type' header to 'application/json'. +16/-0

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[codiumai-pr-agent-free]

PR Description updated to latest commit (2125b11)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[codiumai-pr-agent-free]

PR Review 🔍

⏱️ Estimated effort to review [1-5]	2, because the PR introduces a single method with a clear purpose and straightforward implementation. The changes are localized and do not seem to involve complex logic.
🧪 Relevant tests	No
⚡ Possible issues	Missing Error Handling: The new delete method does not include any specific error handling. It would be beneficial to handle potential errors that could arise during the DELETE request.
🔒 Security concerns	No

[codiumai-pr-agent-free]

PR Code Suggestions ✨

Category	Suggestion	Score
Enhancement	Add error handling to the delete method to improve robustness Consider adding error handling for the delete method to manage exceptions or failed HTTP requests gracefully. This can be done using try-catch blocks or by chaining a .catch() method to the returned promise. apps/platform/src/lib/api-client.ts [80-87] delete<T>(url: string): Promise<T> { return this.request<T>(url, { method: 'DELETE', headers: { 'Content-Type': 'application/json' }, credentials: 'include' - }) + }).catch(error => { + console.error('Failed to delete:', error); + throw error; + }); } Suggestion importance[1-10]: 8 Why: Adding error handling to the delete method is crucial for robustness and to manage exceptions or failed HTTP requests gracefully. This suggestion correctly identifies a significant improvement area in the new code.	8
Possible issue	Handle potential 204 No Content responses in the delete method To ensure the delete method can handle cases where no content is returned (204 No Content), consider checking the response status and handling it accordingly before parsing the response as JSON. apps/platform/src/lib/api-client.ts [80-87] delete<T>(url: string): Promise<T> { return this.request<T>(url, { method: 'DELETE', headers: { 'Content-Type': 'application/json' }, credentials: 'include' - }) + }).then(response => { + if (response.status === 204) { + return null; // or appropriate handling + } + return response.json(); + }); } Suggestion importance[1-10]: 7 Why: Handling 204 No Content responses in the delete method is important for correct API function, especially when no content is expected as a response. This suggestion correctly targets a new method implementation and improves its reliability.	7

[rajdip-b]

🎉 This PR is included in version 1.4.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀