Skip to content

Conversation

@maraf
Copy link
Member

@maraf maraf commented May 4, 2023

  • We need both mono-config.json and blazor.boot.json schemas until we can use new SDK in tree
  • Rename mono-config to blazor.boot.json to unify location where to load config from
  • Drop the need for withStartupOptions to use Wasm SDK path in JS

@maraf maraf added arch-wasm WebAssembly architecture area-Build-mono labels May 4, 2023
@maraf maraf added this to the 8.0.0 milestone May 4, 2023
@maraf maraf self-assigned this May 4, 2023
@ghost
Copy link

ghost commented May 4, 2023

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details
  • We need both mono-config.json and blazor.boot.json schemas until we can use new SDK in tree
  • Rename mono-config to blazor.boot.json to unify location where to load config from
  • Drops the need for withStartupOptions to use Wasm SDK
Author: maraf
Assignees: maraf
Labels:

arch-wasm, area-Build-mono

Milestone: 8.0.0

@pavelsavara
Copy link
Member

This would be ugly merge, other than that look like acceptable temporary solution.

#85730

@maraf
Copy link
Member Author

maraf commented May 4, 2023

I can easily redo it after loader. Mostly text replaces

@maraf maraf merged commit a91d781 into dotnet:main May 12, 2023
@maraf maraf deleted the WasmUnifyConfigLocatioon branch May 12, 2023 17:52
@ghost ghost locked as resolved and limited conversation to collaborators Jun 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

arch-wasm WebAssembly architecture area-Build-mono

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants