-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Obsolete Microsoft.AspNetCore.SpaServices and Microsoft.AspNetCore.No… #12892
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
src/Middleware/NodeServices/samples/NodeServicesExamples/Controllers/HomeController.cs
Outdated
Show resolved
Hide resolved
src/Middleware/SpaServices.Extensions/test/SpaServicesExtensionsTests.cs
Outdated
Show resolved
Hide resolved
src/Middleware/SpaServices/src/Webpack/ConditionalProxyMiddlewareOptions.cs
Show resolved
Hide resolved
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.
Looks good!
Some of the [Obsolete]
attributes might not be needed, but overall great!
Approved by tactics |
4592075
to
718904f
Compare
@ryanbrandenburg could you try rebasing on 3.0? We skipped a couple of the flaky tests you're seeing here. |
613938d
to
e44ed2e
Compare
Is there an example on how to replace calls to UseSpaPrerendering? |
@@ -9,6 +12,7 @@ namespace Microsoft.AspNetCore.NodeServices | |||
/// might change over time (e.g., the process might be restarted), the <see cref="INodeServices"/> instance | |||
/// will remain constant. | |||
/// </summary> | |||
[Obsolete("Use Microsoft.AspNetCore.SpaServices.Extensions")] |
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.
There is no INodeServices
in Microsoft.AspNetCore.SpaServices.Extensions
- what are consumers supposed to be use instead?
[System.ObsoleteAttribute("Use Microsoft.AspNetCore.SpaServices.Extensions")] | ||
public static void AddNodeServices(this Microsoft.Extensions.DependencyInjection.IServiceCollection serviceCollection) { } | ||
[System.ObsoleteAttribute("Use Microsoft.AspNetCore.SpaServices.Extensions")] | ||
public static void AddNodeServices(this Microsoft.Extensions.DependencyInjection.IServiceCollection serviceCollection, System.Action<Microsoft.AspNetCore.NodeServices.NodeServicesOptions> setupAction) { } |
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.
Same question as above - there is no analog in Microsoft.AspNetCore.SpaServices.Extensions
. What should be used instead?
Fixes #11627.
Description
Pursuant to aspnet/Announcements#379 we are marking the following packages as obsolete:
Customer impact
Customers using those packages will have to switch to
Microsoft.AspNetCore.SpaServices.Extensions
.Regression?
No.
Risk
Low. While it's not likely that Obsoleting a class could cause a "bug" in the traditional sense, the migration path to
Microsoft.AspNetCore.SpaServices.Extensions
is not so direct as "If you're using X method switch to Y". Instead developers will have to interact with the various CLIs directly which could lead to some confusion on their part.