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.
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
[blazor] Use JSImport for loading satellite assemblies #46477
[blazor] Use JSImport for loading satellite assemblies #46477
Changes from all commits
82b1279
faf6a1d
7c9c461
631dd40
e5fec45
2dcb6fd
8dca4e3
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I agree that it's fine to remove these tests since they were tied to the old implementation of
LoadCurrentCultureResourcesAsync()
.Thankfully, it looks like this was one of the only cases where we were mocking
IJSUnmarshalledRuntime
for test purposes, so I think it should be unlikely that switching to the newJSImport
/JSExport
interop model will force us to remove a bunch of similar tests in the future.The one exception to this is
WebAssemblyHostBuilder
, which relies heavily onIJSUnmarshalledRuntime
. Tests currently useTestJSUnmarshalledRuntime
to mock JS interop functionality. I would imagine that in this case, we could create anIWebAssemblyHostInterop
interface to provide strongly-typed interop, and we could have a "test" interop class along with the "real" one whose implementation invokes the static[JSImport]
methods. The same pattern could be applied in other cases, if they arise.This isn't really a PR suggestion, just some ideas about the future.