[wasm] Move code around in WBT in preparation for fixes, and cleanups - #88980
Merged
Conversation
.. derived from `BuildTestBase.
.. BlazorWasmProjectProvider, and BlazorWasmTestBase. This commit avoids doing any cleanup, and just moves code around.
|
Tagging subscribers to 'arch-wasm': @lewing Issue Details
|
radical
force-pushed
the
wbt-follow-pr-first
branch
from
July 17, 2023 05:30
bd9e372 to
a6fb183
Compare
Member
Author
|
I would suggest reviewing this commit-wise. |
radical
changed the title
radical
marked this pull request as ready for review
July 17, 2023 08:49
Member
Author
|
Missed updating the list of tests. I'll open a separate PR after these refactoring ones to generate the list at build time. |
ghost
locked as resolved and limited conversation to collaborators
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR is mainly moving code around, and not fixing, cleaning, or rationalizing code.
A follow up PR will start merging common code, fixing testing bundles, icu etc.