Update wasm workload name to wasm-tools
#55413
Conversation
|
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
|
redirect-to is defined here https://github.com/dotnet/designs/blob/main/accepted/2020/workloads/workload-manifest.md#redirects |
|
@joeloff throwing another feature into the mix |
|
@mhutch looks like dotnet/sdk#18166 isn't in yet? We can remove the redirect-to but there is a lot of existing tooling/instruction that uses the old name and things will break until they are updated. |
|
@lewing it looks like redirects won't make it for .NET 6 as we're not 100% confident they won't have unexpected side effects as currently implemented. I think we just have to take the breaking change while we're in preview, sorry :/ |
It's not a problem, I was just hoping to avoid breaking the world again this week. |
|
I'm going to land this later tonight unless there are strong objections. |
|
@naricc - possibly this affects the BDN Microbenchmark runs ? |
lewing
changed the title
wasm-tools
ghost
locked as resolved and limited conversation to collaborators
Change
microsoft-net-sdk-blazorwebassembly-aottowasm-toolsEvery other workload in the file is abstract and probably shouldn't have a short name.