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

📚 Doc: Update intro.md Static Files section #3303

Merged
merged 1 commit into from
Feb 10, 2025

Conversation

lars-schumann
Copy link
Contributor

@lars-schumann lars-schumann commented Feb 9, 2025

Description

In v3 the apps Static method has been removed and its functionality has been moved to the static middleware.

Fixes # (issue)

The given code example has been updated accordingly.

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.

  • Documentation update (changes to documentation)

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

In v3 the apps Static method has been removed and its functionality has been moved to the static middleware.
The given code example has been updated accordingly.
@lars-schumann lars-schumann requested a review from a team as a code owner February 9, 2025 23:54
@lars-schumann lars-schumann requested review from gaby, sixcolors, ReneWerner87 and efectn and removed request for a team February 9, 2025 23:54
Copy link

welcome bot commented Feb 9, 2025

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 Feb 9, 2025

Walkthrough

The documentation for Fiber was updated to change the recommended approach for serving static files. The direct method using app.Static("/", "./public") was replaced with a middleware approach using app.Use("/", static.New("./public")). The intro now clearly recommends the static middleware, reflecting an update in best practices for the Fiber framework.

Changes

File(s) Change Summary
docs/intro.md Replaced direct static file serving via app.Static("/", "./public") with middleware using app.Use("/", static.New("./public")). Updated documentation references.

Sequence Diagram(s)

sequenceDiagram
    participant C as Client
    participant A as Fiber App
    participant M as Static Middleware
    participant FS as File System
    C->>A: Request static resource
    A->>M: Pass request via middleware
    M->>FS: Fetch file from "./public"
    FS-->>M: Return file data
    M-->>A: Deliver file content
    A-->>C: Serve static content
Loading

Possibly related PRs

Suggested labels

📒 Documentation, v3

Suggested reviewers

  • sixcolors
  • gaby
  • efectn
  • ReneWerner87

Poem

Hoppin’ through the code, so light and spry,
I found a new middleware path to fly,
From Static calls to a brand-new way,
Files now gallop without delay,
A joyful rabbit sings as changes beautify!


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 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.

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: 0

🧹 Nitpick comments (1)
docs/intro.md (1)

181-181: Middleware Usage Update
The updated invocation "app.Use("/", static.New("./public"))" properly replaces the deprecated app.Static method according to Fiber v3 guidelines. This change accurately reflects the recommended practice for serving static files. Consider adding a brief note about customizable options for static.New() if your documentation targets more advanced configurations.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 7af9c93 and ba6c5fe.

📒 Files selected for processing (1)
  • docs/intro.md (2 hunks)
🔇 Additional comments (2)
docs/intro.md (2)

166-166: Static Files Section Documentation Update
The revised sentence now directs users to employ the static middleware for serving static files, aligning with Fiber v3 changes. Please verify that the linked static middleware page is updated and provides the necessary context for users.


175-175: Import Addition for Static Middleware
The addition of the import "github.com/gofiber/fiber/v3/middleware/static" is correct and essential for the new static file serving approach. This ensures that the static middleware is available in the code snippets.

@ReneWerner87 ReneWerner87 merged commit 6148c6f into gofiber:main Feb 10, 2025
3 checks passed
Copy link

welcome bot commented Feb 10, 2025

Congrats on merging your first pull request! 🎉 We here at Fiber are proud of you! If you need help or want to chat with us, join us on Discord https://gofiber.io/discord

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants