Feature Suggestions for Enhancing Recovery Middleware

[younesious]

Hey 👋,

tnx for developing such a useful and cool package! I had a chance to explore it, and I found it so elegant.
I have a few suggestions that I believe could enhance the package even further:

1. Structured Logging: Adding support for a structured logging library like zap to improve log clarity and include helpful metadata like timestamps.
2. Customizable Error Responses: Providing options to customize status codes, headers, and error messages in HTTP responses.
3. Context Propagation in gRPC Middleware: Attaching recovery information to the context for downstream access, e.g., ctx = context.WithValue(ctx, "panicDetails", err).

I think these changes would be useful.
HC and "Fire in the hole" — panic-proof. :)

[srahkmli]

Hey Younesious ,

Thank you so much for your kind words and for taking the time to explore the package!
I'm glad you found it elegant and useful.

I especially like the idea of Integrating something like zap to improve log clarity and being more structured.

These are great ideas, and I’ll definitely consider them for future updates. Regarding gRPC, I agree that integrating a client might introduce too many dependencies. It’s something I’d prefer to handle separately, possibly as a distinct module or plugin, to keep the package lightweight and modular.

If you're interested, I’d love to see your contributions or ideas in action!

Thanks again for your support and insights.

"Fire in the hole" indeed, let’s keep things panic-proof! 🔱

[younesious]

ur welcome Srah :) I’d be very happy to contribute to your package. However, I’d like to mention that if you'r not in a hurry and I need some time.

Regarding your point on gRPC: I completely agree with your and Go's philosophy of keeping the package simple, lightweight and modular. To clarify, my suggestion doesn’t involve introducing any new dependencies. Instead, it focuses on enhancing the existing RecoverInterceptor function for gRPC file. Specifically, rather than passing an empty context, we can enhance it by attaching recovery information as I mention above☝️. This approach keeps things simple while allowing downstream middlewares or handlers to access useful details about panics.

But as the owner of the project, we will do whatever you say.
Let me know your thoughts, and I’ll work on the contributions accordingly!

yep, on this repo I think we're on counter-terrorist side :) So just camping and panic-proof!!! 🔱

[srahkmli]

Hey, thanks for the awesome feedback!
I’m totally on board with your idea—adding recovery info to the RecoverInterceptor context is a slick move. It keeps things simple and gives downstream handlers what they need.

No pressure, though!
Take your time, and when you’re ready, hit me with something that blows my mind.

Let’s keep camping and staying panic-proof—counter-terrorist style! 🏴‍☠️