-
Notifications
You must be signed in to change notification settings - Fork 191
Move remaining feature interfaces into Microsoft.AspNetCore.Http.Features
package and namespace
#589
Conversation
/cc @lodejard @davidfowl |
@@ -21,6 +21,7 @@ | |||
"netstandard1.3": { | |||
"dependencies": { | |||
"System.Collections": "4.0.11-*", | |||
"System.ComponentModel": "4.0.1-*", |
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.
Which type requires this?
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.
IServiceProvidersFeature
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.
FYI I moved this from src/Microsoft.AspNetCore.Http.Abstractions/project.json
, same package that interface
came from to this one.
We should look at renaming some of these interfaces on the second pass. /cc @Tratcher |
Just curious: Would the renaming be to add In any case, I suggest filing a separate issue b/c such a renaming is unrelated to #561. That issue is specific to |
Probably adding http to some of them (the ones that relate to http things like form) |
Having a /Features directory inside the Features package is redundant. |
We're supposed to have a directory per namespace and @Eilon asked me to clean up this particular mix. |
I have to agree with @Tratcher, why is it in a features folder? |
Huh? Are you suggesting creating a |
The guideline is to use folders for sub-namespaces. There's no guideline for components in parent namespaces. I think it's fine to put everything in the base directory in this case. |
That means mixing Note moving, say, @Eilon ? |
Oh I didn't realize the files would effectively be in a Just leave it top-level then. |
🆗 |
…tures` package and namespace - related to #561 - move required interfaces and classes down from `Microsoft.AspNetCore.Http.Abstractions` - move everything in the `Microsoft.AspNetCore.Http.Features` into their own directory nit: remove transient dependencies listed in `Microsoft.AspNetCore.Http.Abstractions`'s `project.json`
…o root directory
b026be4
to
10aa15c
Compare
🆙📅 |
Why not include #590? |
Meh, do it so you only have to make one pass of updates. |
🆗 |
….Http` namespace - #590
🆙📅 |
using Microsoft.AspNetCore.Http.Features.Authentication; | ||
using Microsoft.AspNetCore.Http.Features.Authentication.Internal; | ||
using Microsoft.AspNetCore.Http.Features.Internal; |
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.
We still have internal features?
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.
Implementations
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.
Those should go into an internal folder...
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 don't think these should be considered internal |
@davidfowl do you mean I should move all of the implementations into the |
We can file a bug for this. |
|
ResponseCookies.Append()
allocates lots, big lots #561Microsoft.AspNetCore.Http.Abstractions
Microsoft.AspNetCore.Http.Features
into their own directorynit: remove transient dependencies listed in
Microsoft.AspNetCore.Http.Abstractions
'sproject.json