dotnet/aspnetcore

Add HttpContext.Endpoint property

Open

#50,522 opened on Sep 5, 2023

View on GitHub
 (6 comments) (3 reactions) (0 assignees)C# (10,653 forks)batch import
api-approvedarea-networkinghelp wanted

Repository metrics

Stars
 (37,933 stars)
PR merge metrics
 (Avg merge 16d 9h) (258 merged PRs in 30d)

Description

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

ASP.NET Core includes the GetEndpoint and SetEndpoint extension methods for working with endpoints and HttpContext.

I think endpoints have become such an intrinsic feature to ASP.NET Core that we should consider making it a real property on HttpContext. A property would be easier to use (no need to have the right namespace for the extension method) and feel better to use compared to a method.

Describe the solution you'd like

Add HttpContext.Endpoint property.

Additional context

No response

Contributor guide

Research direction
Review the existing GetEndpoint and SetEndpoint extension methods in the aspnetcore repository. Propose adding a property to HttpContext, ensuring backward compatibility and minimal breaking changes. Consider updating the extension methods to work with the new property.
Tech stack
csharp
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#ASP.NET Core
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70