Improve error handling in API requests

[cubxxw]

User description

Enhance the error handling mechanism for API requests to provide clearer feedback and improve user experience during failures.

---

Description

• Enhanced the GitHub Actions workflow for Next.js deployment.
• Improved configuration by changing the generator config file extension.
• Added necessary permissions for deployment.

---

Changes walkthrough 📝

	Relevant files
Configuration changes	nextjs.yml Update Next.js Workflow Configuration                                        .github/workflows/nextjs.yml Updated the generator_config_file path from .mjs to .ts. Added permissions for pages and id-token in the deployment job. +4/-1

---

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

[penify-dev]

PR Review 🔍

⏱️ Estimated effort to review [1-5]	2, because the changes are straightforward and primarily involve configuration updates with minimal complexity.
🧪 Relevant tests	No
⚡ Possible issues	No
🔒 Security concerns	No

[penify-dev]

PR Code Suggestions ✨

Category	Suggestion	Score
Maintainability	Document the permissions section for clarity Ensure that the permissions section is documented to clarify its purpose and usage. .github/workflows/nextjs.yml [91-93] +# Permissions for GitHub Actions permissions: pages: write id-token: write Suggestion importance[1-10]: 7 Why: Documenting the permissions section is beneficial for maintainability, and the suggestion provides a clear improvement by adding a comment, making it actionable.	7
Security	Specify minimum permissions to enhance security Consider specifying the minimum required permissions for the pages and id-token to enhance security. .github/workflows/nextjs.yml [91-93] permissions: - pages: write - id-token: write + pages: write # Consider specifying minimum required permissions + id-token: write # Consider specifying minimum required permissions Suggestion importance[1-10]: 6 Why: The suggestion is relevant as it addresses security concerns, but it lacks specific guidance on what the minimum permissions should be, which limits its effectiveness.	6
Possible issue	Validate the configuration file path to prevent build failures Ensure that the path to the generator_config_file is validated to avoid potential issues during the build process. .github/workflows/nextjs.yml [45] -generator_config_file: ./website/next.config.ts # Ensure this path is correct +generator_config_file: ./website/next.config.ts # Ensure this path is correct; validate path existence Suggestion importance[1-10]: 5 Why: While validating the path is a good practice to prevent build failures, the suggestion does not provide a concrete implementation or method for validation, making it less actionable.	5
Performance	Add a conditional check to optimize the workflow execution Consider adding a conditional check for the environment section to ensure it only runs when necessary. .github/workflows/nextjs.yml [94-96] +if: github.event_name == 'push' # Run only on push events environment: name: github-pages url: ${{ steps.deployment.outputs.page_url }} Suggestion importance[1-10]: 4 Why: While adding a conditional check can optimize workflow execution, the suggestion does not consider the existing context of the deployment job, which may not require such a condition, making it less relevant.	4