Skip to content

🧩 Fix types concerning RestfulApiResponse #375

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

StewEucen
Copy link
Contributor

@StewEucen StewEucen requested review from hecticme, a team and Copilot April 25, 2025 01:57
@StewEucen StewEucen self-assigned this Apr 25, 2025
@StewEucen StewEucen marked this pull request as ready for review April 25, 2025 01:57
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR updates the type annotations for the error template parameter in RestfulApiResponse to use RestfulApiType.Error instead of a generic Record<string, unknown>, ensuring more accurate type definitions.

  • Updated error template annotations in JSDoc.
  • Adjusted inline template definitions across multiple comments.
Comments suppressed due to low confidence (1)

lib/server/restfulapi/interfaces/RestfulApiResponse.js:7

  • Ensure that 'RestfulApiType' is imported or defined in this file to prevent runtime ReferenceError, as its usage in JSDoc requires it to be available.
 * @template {RestfulApiType.Error} E - Type of error.

Copy link

@JYama321 JYama321 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🅾️

@StewEucen StewEucen merged commit df0cb77 into retake/RESTful-API-flushing-structure Apr 25, 2025
2 checks passed
@StewEucen StewEucen deleted the fix/types-concerning-RestfulApiResponse branch April 25, 2025 02:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants