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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add new "MapAction" overloads #30556
Add new "MapAction" overloads #30556
Changes from all commits
7e16e9f
be55d9c
90b86bf
91d6042
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aren't there already Map* extension methods on route builder? Do these not colide because of
Delegate
parameter?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are overloads, but they should only be used for delegates that aren't
RequestDelegate
s. This was also mentioned in dotnet/csharplang#4451 (comment).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need this? As a user, there are alternate ways to re-use the delegate if we need to. I'm also similarly against allowing more than one HTTP attributes per MapAction delegate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that the flexibility of delegates means that we shouldn't need to make routing metadata overly complicated. That's why I removed
IRotePatternMetadata
andIRouteOrderMetadata
in #30563. I also stopped implementingIHttpMethodMetadata
in attributes which caused multiple instances to show up on endpoints that didn't have multiple instances before. #29878 (comment)All that said, this is an overload that already exists for
RequestDelegate
and any argument about reusing theDelegate
, you could make for reusing theRequestDelegate
. I'm just keeping it consistent by adding aDelegate
overload for everyRequestDelegate
overload.