dotnet/aspnetcore

Make OwinFeatureCollection mutable

Open

#2,725 opened on Jan 2, 2018

View on GitHub
 (26 comments) (0 reactions) (0 assignees)C# (10,653 forks)batch import
affected-very-fewarea-networkingenhancementfeature-http-abstractionshelp wantedseverity-nice-to-have

Repository metrics

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

Description

From @Tratcher on Wednesday, October 7, 2015 9:24:33 AM

OwinFeatureCollection does not currently allow you to replace features, so to use it in the pipeline you have to wrap it in a FeatureCollection. Make it mutable instead.

Copied from original issue: aspnet/HttpAbstractions#431

Contributor guide

Research direction
Investigate the current OwinFeatureCollection class, understand why it is immutable, and propose changes to make it mutable while maintaining backward compatibility.
Tech stack
csharp
Domain
backend
Issue type
Refactor
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitC#
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75