deprecate UseMiddlewarWithContainer and remove it from tests and docs #1228
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ccoVeille
suggested changes
Nov 20, 2024
ccoVeille
approved these changes
Nov 20, 2024
coolwednesday
approved these changes
Nov 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Template
Description:
UseMiddlewareWithContainer.Reason for Deprecation:
We are deprecating the
UseMiddlewareWithContainerfeature due to architectural considerations. Allowing middleware to access databases or caches introduces unnecessary complexities.By removing this support, we aim to encourage a cleaner separation of concerns, ensuring that middleware remains focused on its intended purpose. This change will help in maintaining the simplicity and integrity of our framework.
Checklist:
goimportandgolangci-lint.Thank you for your contribution!