feat: add middleware comp proper registrations #3956
Merged
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.
Description
Separating the middleware changes from PR:
#3949
For each dapr release there is an endgame task to ensure that components are properly registered across contrib and dapr/dapr. I took the time to fix all the issues that I came across, cross referencing the docs. This PR adds missing metadata.yaml files.
You will also see TODO comments here and there. That is from me going through the code to manually create the metadata.yaml files and add todos i deemed necessary for the component. I also updated any interface{} to any that I came across along the way.
Yes, I did cross ref the docs too so the links should be 99.9% correct unless I made a typo or missed something accidentally.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #[issue number]
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:
Note: We expect contributors to open a corresponding documentation PR in the dapr/docs repository. As the implementer, you are the best person to document your work! Implementation PRs will not be merged until the documentation PR is opened and ready for review.