Discussion: New Community-Requested Examples

[coderabbitai]

This issue is opened to discuss and identify new examples that are important to the GoFiber community. Your suggestions and ideas are welcome!

Referenced from PR: #2703

Requested by: @ReneWerner87

[ReneWerner87]

@coderabbitai Please suggest possible other examples based on the questions from the gofiber/fiber repository which are already closed or still open
There you can find the examples that are most interesting for the community

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

@ReneWerner87, based on the open and closed issues in the gofiber/fiber repository, here are some suggested examples that might be valuable additions to the gofiber/recipes repository:

1. Parsing Form Data into Maps and Slices

   • Reference: Issue #3216
   • Description: Users are encountering issues when parsing form data into maps and slices using BodyParser. An example demonstrating how to correctly parse application/x-www-form-urlencoded data into Go maps, structs, and slices would be beneficial. This could include handling complex form inputs and nested data structures.

2. Implementing HTTP 103 Early Hints

   • Reference: Issue #3211
   • Description: With the proposal to add support for HTTP 103 Early Hints in Fiber, an example showcasing how to implement Early Hints to improve page load times would be helpful. This could demonstrate sending preliminary responses to clients to initiate resource preloading while the server prepares the final response.

3. Handling WebSocket Connections and Shared Data

   • Reference: Issue #3195
   • Description: There are questions about managing shared data across multiple WebSocket connections, especially when multiple clients are connected from the same browser instance. An example illustrating how to handle WebSocket connections, maintain state, and prevent data conflicts would be valuable.

4. Serving Multiple Frontend Frameworks with Fiber

   • Reference: Issue #3192
   • Description: Users are interested in serving frontend frameworks like Angular with server-side rendering (SSR) using Fiber. An example detailing how to integrate Fiber with Angular's SSR, possibly using a reverse proxy or middleware to handle SSR, would address this need.

5. Implementing Retry and Circuit Breaker Patterns in Proxy Middleware

   • Reference: Issue #3191
   • Description: An example demonstrating how to implement custom retry logic and circuit breaker patterns using Fiber's proxy middleware would be beneficial. This could help users enhance the reliability of their microservices by handling network failures gracefully.

6. Graceful Shutdown and Context Cancellation

   • Reference: Issue #3186
   • Description: There are concerns about context cancellation when running tests. An example showing how to handle context propagation and cancellation in Fiber applications, ensuring that resources are cleaned up properly during shutdown or testing, would be helpful.

7. Using Fiber with OpenAPI 3 (Swagger) Integration

   • Reference: Issue #3118
   • Description: Users are looking to integrate Fiber with OpenAPI 3 specifications using libraries like kin-openapi. An example demonstrating how to generate Swagger documentation from Fiber applications and how to validate requests against OpenAPI schemas would be beneficial.

8. Dynamic Route Management in Fiber

   • Reference: Issue #3098
   • Description: There's interest in dynamically adding and removing routes at runtime. An example that illustrates how to manage routes dynamically, leveraging Fiber’s app.Add() and app.Stack() methods, would help users who need flexible routing capabilities.

9. Custom Error Handling with Sentry Integration

   • Reference: Issue #3103
   • Description: Users have questions about capturing detailed stack traces with Sentry in Fiber applications. An example showing how to integrate Sentry for error monitoring, including custom error handlers that capture exceptions with full context, would be valuable.

10. Implementing Advanced Caching Strategies

    • Reference: Issue #3097
    • Description: There are proposals to enhance cache mechanisms in middleware. An example demonstrating advanced caching strategies, possibly with group keys or custom key generators using UUIDs, would assist users in optimizing their applications' performance.

These examples address common challenges and questions from the community and would make great additions to the recipes repository. They can help users better understand how to implement complex functionality in their Fiber applications.

🔗 Analysis chain

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Fetch the last 100 open and closed issues from the gofiber/fiber repository
gh issue list -R gofiber/fiber --state all --limit 100 --json number,title,body,state,url

Length of output: 130742

[stale]

👋 Hello. Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Thank you for your contributions.

[giancarlosisasi]

We also need correct examples/recipes of how to integrate fiber with gqlgen including subscription!

[ReneWerner87]

Keeping this open, but the list above is from November 2024 and two of the ten have since been covered. Checked each against the current 87 recipes so the backlog reflects reality:

#	Suggestion	Status
1	Parsing form data into maps and slices	missing
2	HTTP 103 Early Hints	missing
3	WebSocket connections and shared data	partly. websocket and websocket-chat exist, but neither shows state shared across connections, which was the actual question
4	Serving Angular with SSR	missing. There are svelte-netlify, sveltekit-embed, react-router and template-asset-bundling, but nothing Angular
5	Retry and circuit breaker in proxy middleware	missing. dummyjson proxies but has no resilience logic
6	Graceful shutdown and context cancellation	covered by graceful-shutdown, plus tableflip for graceful upgrades
7	OpenAPI 3 / Swagger integration	covered by openapi and swagger
8	Dynamic route management	missing
9	Custom error handling with Sentry	missing. recover covers the middleware side, monitoring-with-apitally covers monitoring, neither covers Sentry
10	Advanced caching strategies	missing. No cache-focused recipe in the index

Also worth pulling out of the thread, since it is the only request here from an actual user rather than a generated suggestion:

We also need correct examples/recipes of how to integrate fiber with gqlgen including subscription!

That one connects to something else. #3046 was opened because the graphql recipe's README mentioned gqlgen while the code used graphql-go. The README has since been corrected and I closed that issue today, but two separate people arriving at this repo expected gqlgen and did not find it. The graphql recipe covers graphql-go only, and subscriptions are not demonstrated at all.

So a gqlgen recipe with subscriptions looks like the highest-value item on this list: it is the only one someone actually asked for, and there is documented evidence of people looking for it.

No action taken on any of these, they are all new recipes rather than fixes. Flagging the triage so the list is usable rather than two years stale.

---

Generated by Claude Code

[annaveretennykova]

@ReneWerner87 I'd like to work on #1, the form-data parsing example (urlencoded --> maps/structs/slices). Will match the existing recipe structure. Scope look right?

[ReneWerner87]

Ok thx