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 gofiber compability from v2 to v3 #103

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

adrieljss
Copy link

@adrieljss adrieljss commented Dec 7, 2024

Here are the changes:

  • v3 drops support for the file system middleware, it is now changed to the Static Middleware. (Specified Here).
  • v3 Handler callbacks now needs non-pointer as parameter (*fiber.Ctx -> fiber.Ctx)
  • Changed redirection code. (Specified Here).

Might be breaking changes since v3 only supports Go 1.23+ (Specified Here)

Summary by CodeRabbit

  • New Features

    • Upgraded to the latest version of the Fiber framework, enhancing performance and compatibility.
  • Bug Fixes

    • Improved readability and functionality of redirect handling in the application.
  • Documentation

    • Updated test cases to ensure they align with the new framework, maintaining validation of Swagger API endpoints.

Copy link

coderabbitai bot commented Dec 7, 2024

Walkthrough

The changes in this pull request involve upgrading the gofiber/fiber package from version 2 to version 3. This upgrade includes modifications to middleware, specifically replacing the filesystem middleware with static middleware. Additionally, function signatures have been updated to accept fiber.Ctx instead of *fiber.Ctx. The error handling for template parsing remains unchanged, but the redirect handling has been improved for readability. The swagger_test.go file has also been updated to reflect the new import for the Fiber package, ensuring that existing tests continue to function correctly.

Changes

File Change Summary
swagger.go Upgraded from gofiber/fiber/v2 to gofiber/fiber/v3, replaced filesystem middleware with static, updated function signatures to accept fiber.Ctx, improved redirect handling.
swagger_test.go Updated import from gofiber/fiber/v2 to gofiber/fiber/v3, no structural changes to test functions, maintained existing logic.

Possibly related PRs

Poem

🐇 In the land of code where fibers weave,
A hop to version three, we believe!
Static files now dance in the light,
Redirects are clearer, oh what a sight!
With tests still strong, they leap and bound,
In the garden of code, new joys abound! 🌼


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 or @coderabbitai title 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

@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 (2)
swagger.go (1)

38-38: LGTM: Handler signature updated per v3 requirements

The handler signature has been correctly updated to use non-pointer fiber.Ctx parameter as required by fiber v3.

Consider adding a comment to document this breaking change for better visibility to package users.

swagger_test.go (1)

8-8: Consider adding tests for v3-specific features

While the import has been correctly updated to fiber v3, consider adding test cases to verify:

  1. Error handling with non-pointer context
  2. Static middleware functionality
  3. New redirection behavior
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between e2d9e99 and 6ad38d2.

⛔ Files ignored due to path filters (2)
  • go.mod is excluded by !**/*.mod
  • go.sum is excluded by !**/*.sum, !**/*.sum
📒 Files selected for processing (2)
  • swagger.go (3 hunks)
  • swagger_test.go (1 hunks)
🔇 Additional comments (2)
swagger.go (2)

69-69: LGTM: Redirection code updated to v3 syntax

The redirection code has been updated to use the new method chaining syntax (Redirect().Status().To()), which improves readability and follows fiber v3 standards.


10-12: Verify utils package compatibility with fiber v3

While the fiber package has been correctly upgraded to v3, the utils package remains at v2. This version mismatch might cause compatibility issues.

✅ Verification successful

Let me try a different approach to verify the compatibility between fiber v3 and utils package.


Utils package version is compatible with Fiber v3

The utils package version v2.0.0-beta.7 is actually aligned with Fiber v3.0.0-beta.3 as shown in the go.mod file. Both packages are using beta versions that are meant to work together, and the version difference (v2 vs v3) is not a compatibility concern in this case.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if fiber v3 has any compatibility requirements for utils package
gh api graphql -f query='
{
  repository(owner: "gofiber", name: "fiber") {
    object(expression: "v3") {
      ... on Commit {
        file(path: "go.mod") {
          object {
            ... on Blob {
              text
            }
          }
        }
      }
    }
  }
}'

Length of output: 322


Script:

#!/bin/bash
# Check the current go.mod file to see utils package requirements
cat go.mod

# Search for utils package usage patterns in the codebase
rg "github.com/gofiber/utils" -A 2 -B 2

Length of output: 2409

Comment on lines +71 to +74
return static.New("/", static.Config{
FS: swaggerFiles.FS,
Browse: true,
})(c)
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Security: Review static middleware configuration

The static middleware is configured with Browse: true, which could potentially expose sensitive files. Consider if directory browsing is necessary for your use case.

 return static.New("/", static.Config{
   FS:     swaggerFiles.FS,
-  Browse: true,
+  Browse: false,
 })(c)
📝 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
return static.New("/", static.Config{
FS: swaggerFiles.FS,
Browse: true,
})(c)
return static.New("/", static.Config{
FS: swaggerFiles.FS,
Browse: false,
})(c)

@ReneWerner87
Copy link
Member

Thx for your work

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