Skip to content
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

Update intro.md #3222

Closed
wants to merge 1 commit into from
Closed

Update intro.md #3222

wants to merge 1 commit into from

Conversation

firevenus
Copy link

Update it to install and with version.

Description

Please provide a clear and concise description of the changes you've made and the problem they address. Include the purpose of the change, any relevant issues it solves, and the benefits it brings to the project. If this change introduces new features or adjustments, highlight them here.

Fixes # (issue)

Changes introduced

List the new features or adjustments introduced in this pull request. Provide details on benchmarks, documentation updates, changelog entries, and if applicable, the migration guide.

  • Benchmarks: Describe any performance benchmarks and improvements related to the changes.
  • Documentation Update: Detail the updates made to the documentation and links to the changed files.
  • Changelog/What's New: Include a summary of the additions for the upcoming release notes.
  • Migration Guide: If necessary, provide a guide or steps for users to migrate their existing code to accommodate these changes.
  • API Alignment with Express: Explain how the changes align with the Express API.
  • API Longevity: Discuss the steps taken to ensure that the new or updated APIs are consistent and not prone to breaking changes.
  • Examples: Provide examples demonstrating the new features or changes in action.

Type of change

Please delete options that are not relevant.

  • New feature (non-breaking change which adds functionality)
  • Enhancement (improvement to existing features and functionality)
  • Documentation update (changes to documentation)
  • Performance improvement (non-breaking change which improves efficiency)
  • Code consistency (non-breaking change which improves code reliability and robustness)

Checklist

Before you submit your pull request, please make sure you meet these requirements:

  • Followed the inspiration of the Express.js framework for new functionalities, making them similar in usage.
  • Conducted a self-review of the code and provided comments for complex or critical parts.
  • Updated the documentation in the /docs/ directory for Fiber's documentation.
  • Added or updated unit tests to validate the effectiveness of the changes or new features.
  • Ensured that new and existing unit tests pass locally with the changes.
  • Verified that any new dependencies are essential and have been agreed upon by the maintainers/community.
  • Aimed for optimal performance with minimal allocations in the new code.
  • Provided benchmarks for the new code to analyze and improve upon.

Commit formatting

Please use emojis in commit messages for an easy way to identify the purpose or intention of a commit. Check out the emoji cheatsheet here: CONTRIBUTING.md

Update it to install and with version.
@firevenus firevenus requested a review from a team as a code owner November 29, 2024 18:34
@firevenus firevenus requested review from gaby, sixcolors, ReneWerner87 and efectn and removed request for a team November 29, 2024 18:34
Copy link

welcome bot commented Nov 29, 2024

Thanks for opening this pull request! 🎉 Please check out our contributing guidelines. If you need help or want to chat with us, join us on Discord https://gofiber.io/discord

Copy link
Contributor

coderabbitai bot commented Nov 29, 2024

Walkthrough

The documentation for the Fiber web framework has been updated to reflect a change in the installation command, shifting from go get github.com/gofiber/fiber/v3 to go install github.com/gofiber/fiber/v2@latest. This modification affects how users obtain the framework. Additionally, the documentation clarifies that values returned from fiber.Ctx are mutable and reused across requests, providing guidance on their correct usage. The "Hello, World" example has been updated to reference the new installation command, while the routing section remains unchanged.

Changes

File Change Summary
docs/intro.md Updated installation command from go get github.com/gofiber/fiber/v3 to go install github.com/gofiber/fiber/v2@latest. Clarified mutability of context values in fiber.Ctx and provided usage examples. Retained "Hello, World" example with updated command reference.

Possibly related PRs

  • 📚 Doc: Update intro documentation #3204: This PR updates the introductory documentation for Fiber, including the installation section, which is directly related to the changes made in the main PR regarding the installation command for the Fiber web framework.
  • 📚 Doc: Updates to Context documentation #3206: This PR enhances the Context documentation, which includes clarifications about context values, aligning with the main PR's focus on the mutability of values returned from fiber.Ctx.

Suggested labels

📒 Documentation

Suggested reviewers

  • sixcolors
  • gaby
  • ReneWerner87

🐰 In the garden of code, we hop with glee,
A new command for Fiber, as fresh as can be!
Context values mutable, now clear as the day,
With examples to guide us, we’ll code and play!
So let’s build our apps, with joy and delight,
For in every new change, our future shines bright! 🌟


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?

❤️ Share
🪧 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 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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Outside diff range and nitpick comments (3)
docs/intro.md (3)

Line range hint 8-8: Update placeholder release date

The documentation contains a placeholder for the v3 release date: "Month xx, 202x". This should be updated with the actual release date.


Line range hint 22-73: Excellent explanation of context value handling

The Zero Allocation section provides clear guidance on context value handling, with good examples and references. Consider adding a warning box or visual highlight for the critical rule: "you must only use context values within the handler".

Consider adding a highlighted warning:

### Zero Allocation

+> ⚠️ **Important**: Context values are only valid within handlers. Using them outside handlers can lead to data races and unexpected behavior.
+
Fiber is optimized for **high performance**...

Update installation command to use v3

The code examples consistently use v3 imports, but there's one inconsistency in the installation command that needs to be updated:

-go install github.com/gofiber/fiber/v2@latest
+go install github.com/gofiber/fiber/v3@latest
🔗 Analysis chain

Line range hint 75-186: Ensure version consistency in code examples

The code examples need to be updated to consistently use v3 imports. Currently, there's a mix of versions in the examples.

Let's verify the version references in the code examples:

Update all import statements to use v3:

-import "github.com/gofiber/fiber/v2"
+import "github.com/gofiber/fiber/v3"
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for version references in code blocks
rg -U 'fiber/v[23]' docs/intro.md

Length of output: 152


Script:

#!/bin/bash
# Let's search for any other potential version references in the entire file
rg -U '(?:fiber/v\d|@v\d)' docs/intro.md

Length of output: 159

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 89452fe and 075b64e.

📒 Files selected for processing (1)
  • docs/intro.md (1 hunks)

@@ -17,7 +17,7 @@ First, [download](https://go.dev/dl/) and install Go. Version `1.22` or higher i
Installation is done using the [`go get`](https://pkg.go.dev/cmd/go/#hdr-Add_dependencies_to_current_module_and_install_them) command:

```bash
go get github.com/gofiber/fiber/v3
go install github.com/gofiber/fiber/v2@latest
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Critical version mismatch in installation instructions

The documentation header states "These docs are for Fiber v3", but the installation command references v2. This inconsistency could mislead users about which version they're installing.

If this is meant to be v3 documentation, update the command:

-go install github.com/gofiber/fiber/v2@latest
+go install github.com/gofiber/fiber/v3@latest
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
go install github.com/gofiber/fiber/v2@latest
go install github.com/gofiber/fiber/v3@latest

@gaby
Copy link
Member

gaby commented Nov 29, 2024

@firevenus The main branch is the code for GoFiber v3. The v2 branch is for GoFiber v2.

@gaby gaby closed this Nov 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants