Only enable scoped CSS when using Razor SDK

[MackinnonBuck]

Only enable scoped CSS when using Razor SDK

The scoped CSS feature has a dependency on targets defined in the Razor SDK. In order to allow the StaticWebAssets SDK to be used without the Razor SDK, this PR enables scoped CSS only when the Razor SDK is used.

Fixes dotnet/aspnetcore#47314

[ghost]

Thanks for your PR, @MackinnonBuck.
To learn about the PR process and branching schedule of this repo, please take a look at the SDK PR Guide.

[javiercn]

For extra points, we should also clean up the other locations where the StaticWebAssets SDK depends on the Razor SDK.

I found the following targets AssignRazorComponentTargetPaths and AssignRazorComponentTargetPaths the one in

The one in JS modules seems like an error. For the other two, something in the Razor SDK should turn on the feature (instead of us) and define the dependency on the scoped CSS step so that it is the Razor compiler the one that controls when the feature is on and how it applies.

https://github.com/search?q=repo%3Adotnet%2Fsdk+AssignRazorComponentTargetPaths+lang%3Axml&type=code

[MackinnonBuck]

@javiercn that all sounds good to me. Do you mind if I address those items in a follow-up PR so we unblock #31154?

[javiercn]

@MackinnonBuck nope.

This is good to go.

We want, if possible to keep the layering clean where dependencies flow:

flowchart LR
BlazorSdk-->WasmSdk
BlazorSdk-->RazorSdk
WasmSdk-->StaticWebAssetsSdk
RazorSdk-->StaticWebAssetsSdk

Loading