-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Added Microsoft.Extensions.Features Project #31746
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
Conversation
1. Added initial structure of Microsoft.Extensions.Features project. 2. Updated `HttpAbstractions` solution filter and AspNetCore.sln root solution to include new project. As part of #31723
@MCCshreyas this is one I'd want the team to do to avoid any lag or back and forth. Thanks for your efforts here! |
Will it be ok, if I proceed with a task that @pranavkm mentioned, my target is to finish this one today itself. If I face any difficulties, and look like obstacles I will close this PR then! But if everything goes correct and if I managed to get this all done today itself, so should I still close my PR, OR maybe someone from the team can proceed with my changes if those changes are hard and need some internal discussion before going. |
This one is tricky because we need to spend time dealing with the implications of the breaking change and messing with type forwards. It's a little intricate and not a good pick for a contribution |
@davidfowl Let me try! 😄 |
1. Moved `IFeatureCollection`, `FeatureCollection` to new assembly. 2. Added `TypeForwardFrom` and `TypeForwardTo` Attribute for those types. 3. Added entries in ProjectReferences.props and SharedFramework.Local.props based on ReferenceResolution.md document. 4. Updated PublicAPI files for both project to reflect new changes.
Help on this would be appreciated. 😄 |
I'd rather not. Can you take on another issue please. As I said before this one requires a bit more care and it would be better for the team to handle it. It's not that it couldn't be done by yourself, but we didn't mark it "help wanted" for a very specific reason. |
Ummm. I keep those issues for other people who are new to the repo and or the first time. I took this issue because based on the issue description, it was looking not very hard. But as you suggested, these changes need to be discussed internally before proceed, so I will close this PR as of now! But later if you guys, found I was on the correct track of changes and also need some more changes, then please feel free to re-open this PR, I like to continue from there as well! Thanks, 😑😊 |
Tasklist
Microsoft.AspNetCore.Http.Features
to targetnet6.0
and stop publishing it as a NuGet package.As part of #31723
cc @pranavkm @davidfowl