fix: fix env

[Akagi201]

Summary by CodeRabbit

• Configuration

  • Updated environment variable naming from PARALLEL_EVM_EXPLORER_SERVER to NEXT_PUBLIC_API_SERVER

• Development

  • Added debug logging for API request URLs
  • Modified API server URL configuration in frontend utilities

[coderabbitai]

Walkthrough

The pull request involves updating the environment variable used for specifying the server URL in both the frontend README and the API utility file. The change transitions from PARALLEL_EVM_EXPLORER_SERVER to NEXT_PUBLIC_API_SERVER, indicating a shift in the naming convention for environment variables. Additionally, the fetchRequest function in the API utility file has been modified to reflect this new variable, with added console logs for improved debugging of the request URL construction process.

Changes

File	Change Summary
frontend/README.md	Updated environment variable from PARALLEL_EVM_EXPLORER_SERVER to NEXT_PUBLIC_API_SERVER
frontend/src/utils/api.js	- Replaced environment variable in URL construction - Added console.log statements for debugging

Possibly related PRs

• chore: rename env #4: Similar modification of environment variable in frontend/src/utils/api.js, changing the base URL naming convention.

---

📜 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 97d1241 and af8f3ef.

📒 Files selected for processing (2)

• frontend/README.md (1 hunks)
• frontend/src/utils/api.js (1 hunks)

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

• frontend/README.md
• frontend/src/utils/api.js

---

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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. (Beta)
• @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: 0

🧹 Nitpick comments (2)

frontend/src/utils/api.js (1)

15-15: Remove temporary debugging logs.

These console.log statements appear to be temporary debugging additions. They should be removed before merging to keep the codebase clean.

-    console.log("url1", url);
     url = `${url}?${queryString}`;
-    console.log("url2", url);
...
-    console.log("url3", `${process.env.NEXT_PUBLIC_API_SERVER}${url}`);

Also applies to: 17-17, 25-25

frontend/README.md (1)

15-15: Add migration note for existing users.

While the environment variable update is documented, consider adding a note for existing users about migrating from PARALLEL_EVM_EXPLORER_SERVER to NEXT_PUBLIC_API_SERVER.

Add this section before the environment variable example:

 .env
 
+> **Note:** If you're upgrading from a previous version, rename `PARALLEL_EVM_EXPLORER_SERVER` to `NEXT_PUBLIC_API_SERVER` in your .env file.
+
 ```sh
 NEXT_PUBLIC_API_SERVER=http://<your-server-host>:<port>

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

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

<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between 79223d608957aa8321293e476a33f684773202bc and 97d124152de539a32ddd76bd1a5456a145095a1a.

</details>

<details>
<summary>📒 Files selected for processing (2)</summary>

* `frontend/README.md` (1 hunks)
* `frontend/src/utils/api.js` (1 hunks)

</details>

<details>
<summary>🔇 Additional comments (1)</summary><blockquote>

<details>
<summary>frontend/src/utils/api.js (1)</summary>

`27-27`: **Verify deployment configurations for the new environment variable.**

The change from `PARALLEL_EVM_EXPLORER_SERVER` to `NEXT_PUBLIC_API_SERVER` follows Next.js conventions for public environment variables. However, this is a breaking change that requires updates to deployment configurations.

Run this script to check for any remaining references to the old environment variable:

</details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->