Code Review

This pull request addresses context key collisions by using unexported key types, which is a great improvement. However, the new FromContext function in the jwt package introduces a critical bug that can cause a panic. Additionally, the examples in the paseto README demonstrate an unsafe usage of its new FromContext function, which can also lead to panics. I've provided suggestions to fix these issues.

Pull Request Overview

This PR addresses context key collisions by replacing string-based context keys with unexported typed context keys in both JWT and PASETO middleware packages. The changes prevent potential conflicts when multiple packages store values in the Fiber context using the same string keys.

• Introduces unexported contextKey type and typed constants for context storage
• Removes configurable ContextKey field from middleware configuration
• Adds FromContext helper functions for type-safe context value retrieval

Reviewed Changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated 4 comments.

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

Code Review

This pull request correctly addresses context key collisions by using unexported key types for storing data in the context, a recommended practice in Go. The changes are applied to both the jwt and paseto middleware. However, I've identified a critical issue in the jwt package where the new FromContext function can cause a panic if the token is not found in the context. Additionally, the usage examples in the jwt README have not been updated to reflect the API changes, which will lead to runtime panics for users who copy the code. The changes for the paseto package appear to be correct and well-documented.

Code Review

This pull request refactors the JWT and Paseto middleware to use unexported context keys, which is a great improvement to prevent key collisions. The implementation is solid and follows Go best practices. My review focuses on improving the documentation to match the code changes and to promote safer usage patterns in the examples. I've pointed out some inconsistencies in the JWT README's configuration table and suggested making the code examples in the Paseto README more robust by adding checks for nil values before type assertions to prevent potential panics.