Added env variable NEXT_PUBLIC_API_URL
Description
Added env variable NEXT_PUBLIC_API_URL in .env.example files
Related Issues
Closes #<issue_number>
Checklist
- [x] My code follows the code style of this project.
- [x] I have performed a self-review of my code.
- [x] I have commented my code, particularly in hard-to-understand areas.
- [x] I have updated the documentation, if necessary.
- [x] I have added tests that prove my fix is effective or my feature works.
- [x] New and existing tests pass locally with my changes.
Screenshots (if applicable)
Additional Notes
I find it useful for me to query the API from web and app
Summary by CodeRabbit
-
New Features
- Introduced a new environment variable
NEXT_PUBLIC_API_URLfor client-side applications, allowing configuration of the API endpoint.
- Introduced a new environment variable
-
Chores
- Moved the existing
NEXT_PUBLIC_DOCS_URLvariable to a new line without changing its value.
- Moved the existing
@OsoThevenin is attempting to deploy a commit to the Hayden Bleasel Team on Vercel.
A member of the Team first needs to authorize it.
[!IMPORTANT]
Review skipped
Review was skipped due to path filters
:no_entry: Files ignored due to path filters (1)
.github/workflows/build.ymlis excluded by none and included by noneCodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including
**/dist/**will override the default block on thedistdirectory, by removing the pattern from both the lists.You can disable this status message by setting the
reviews.review_statustofalsein the CodeRabbit configuration file.
📝 Walkthrough
📝 Walkthrough
Walkthrough
The changes introduce a new environment variable NEXT_PUBLIC_API_URL set to http://localhost:3002 in the .env.example files of three applications: api, app, and web. Additionally, the existing variable NEXT_PUBLIC_DOCS_URL is moved to a new line in the api application's .env.example file, but its value remains unchanged. The overall structure of the environment variables is preserved across all files.
Changes
| File Path | Change Summary |
|---|---|
| apps/api/.env.example | Added NEXT_PUBLIC_API_URL="http://localhost:3002"; moved NEXT_PUBLIC_DOCS_URL to a new line (value unchanged). |
| apps/app/.env.example | Added NEXT_PUBLIC_API_URL="http://localhost:3002". |
| apps/web/.env.example | Added NEXT_PUBLIC_API_URL="http://localhost:3002". |
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
🪧 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
@coderabbitaiin 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
@coderabbitaiin 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 pauseto pause the reviews on a PR. -
@coderabbitai resumeto resume the paused reviews. -
@coderabbitai reviewto trigger an incremental review. This is useful when automatic reviews are disabled for the repository. -
@coderabbitai full reviewto do a full review from scratch and review all the files again. -
@coderabbitai summaryto regenerate the summary of the PR. -
@coderabbitai resolveresolve all the CodeRabbit review comments. -
@coderabbitai configurationto show the current CodeRabbit configuration for the repository. -
@coderabbitai helpto get help.
Other keywords and placeholders
- Add
@coderabbitai ignoreanywhere in the PR description to prevent this PR from being reviewed. - Add
@coderabbitai summaryto generate the high-level summary at a specific location in the PR description. - Add
@coderabbitaianywhere in the PR title to generate the title automatically.
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.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| next-forge | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Nov 25, 2024 3:49pm |
@OsoThevenin Is this env var required anywhere currently? Or is it just future-facing?
@haydenbleasel this is future-facing. I thought it could be useful
:rocket: PR was released in v2.18.2 :rocket: